Sergey Sharybin
c847198a7b
Instead of allocating scheduler and starting threads on every object_update call make it so scheduler is global and threads are always ready to run. This was we could avoid quite hacky thing which is counting how much objects need to be updated before starting threaded update. It'll also allow using the same scheduler to do all sorts of tasks, not only objects update in the same scheduler. This is nice from load balancing point of view. Couple of changes were needed to be done in task scheduler itself: - Free tas before sending notifier. - Free TaskThread structures outside from thread. This is needed to make it possible use begin/end threaded malloc from the main thread before/after running the pool. Without this change it was possible that allocation will switch to non-thread mode while thread is freeing the task. This required storing TaskThread array in Scheduler, but it's not so much bad actually, since it also reduces memory overhead caused by per-thread allocation.