Writing a blog post on Data Oriented Design. Any skeptics want to share their worries/criticisms? Looking to address some of the most common ones.
Näytä tämä ketju
-
With respect to threading, do you rely on the OS's thread scheduler (1 task per thread) or do you partition the task space into sub-groups that you assign to each thread? If you have lots of tasks, relying on OS's scheduler might not be the best idea:https://en.wikipedia.org/wiki/Partition_problem …
There is 1 thread per core (or fewer threads than cores, configurable via .ini). All tasks are put into a queue and picked up by workers. There is no main thread, per se. main thread gets stuff going then just becomes a worker.
-
-
If enabled, each worker has an affinity set to a core #. So the third worker will always run on the third core. You can set groups of tasks to only run on certain cores (ie, async tasks never run on “frame reserved” cores.)
-
Thank you for the explanation. The model looks to me like Cilk's model ( https://en.wikipedia.org/wiki/Cilk ) which i liked a lot, but ultimately failed. IMHO, in the end all that matters is if the part of the model that depends on certain programmer abilities, can be satisfied or not.
- Näytä vastaukset
Uusi keskustelu -
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.