Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a question about Symbian active objects handling. What’s the problem: my program runs in 1 thread and have pretty much active objects in it. As per my logs, I see strange pauses in tasks processing. My program have about 30 simultaneously active objects in one ActiveScheduler. Is it okay?
Any Symbian Active Scheduler can handle pretty much as many Active Objects as you need.
Obviously, each added active object has a tiny performance impact on the whole scheduler but 30 is well within acceptable range.
You do have to remember this is all based on cooperative multitasking, though. If too many requests get completed too fast and active objects take too long to run, the time it takes for the scheduler to call RunL() on a specific single active object can become unacceptable for your application.