4 ms·
main thread has to go somewhere. :\ Maybe knowing consumers will probably have more than 2 cores will make games optimise better for parellelism, it's not like
by dijit 10y ago
main thread has to go somewhere. :\
Maybe knowing consumers will probably have more than 2 cores will make games optimise better for parellelism, it's not like the engine programmers _cant_ do it, they do it all the time with GPUs.
- gcp 10y agoGPU parallelism is very different from main-core parallelism. The GPU is an entirely different architecture than the CPU. The stuff that's still on the CPU are things that don't trivially parallelize to begin with.
- dijit 10y agoI can give you an example in my actual work; When making AI bots it's quite common to have all of the work of processing the AI it's own thread, so each rendered frame will do all calculations for all bots. That in of itself would be cheap, except it has to share it's core with a bunch of other crap. With 2 cores you can have a main thread for updating the screen and then an "everything else" thread. If you can't be sure people will be playing with >2 cores then you have to keep your budgets down to 2 cores when developing and that's quite limiting. it's not that it's "hard" to parralellise(?), it's that you run out of resources super quick if you make assumptions about CPU topology.