Performance penalty due to large amount of suspended tasks

evgeny-erlihman wrote on Thursday, February 08, 2018:


I am working on an app that uses static allocations for all it’s tasks. I have a task that needs to run from time to time, not frequntly. My question is, what would be more efficient, create it at startup and keep it in suspended mode. Or create/destroy it every time i need it to run (using the same statically allocated memory). If it is in suspended mode, would it introduce more latency in the scheduler (assuming i have several similiar tasks), or is it neglectable?


heinbali01 wrote on Friday, February 09, 2018:

I would leave the task that has nothing to do, in suspended or in blocked mode.
A task that is not active does not make the scheduler any slower.
Tasks that are runnable sit in a different (internal) list, sorted on priority.