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
-
When i hear about multithreading stuff the questions i have are: Do you have a dynamic model (spawning tasks at runtime?). Do you use a fork-join model? Do you do task stealing? Do you do partitioning? Do you have task dependencies? If yes what do you do about deadlocks?
-
-
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.
- 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.