Dnes vyšel zajímavý článek na The Inquirer. Někdo z redakce hovořil s vývojáři her o možnosti využití quad-core:

Citace Původně odeslal The Inquirer, Fuad Abazovic
We spoke with many developers including some big names and we learned that they can’t make much sense out of quad or more core CPUs. They confirm that they can put two cores to good use but not much more. The main problem is that the performance is far from scalable.

You have to spend both time and money to resource the programmer to try to make sense out f the dual core CPU. It takes up to a year to optimise the game for more threads and even if you make the perfect job you can count on twenty to thirty percent performance increase, and this is the best case scenario.

Once you start making the multi threaded game you end up making and having the multithreaded bugs as well.

You can keep one core busy with the physics and collision detection, second core will have to wait for the score to move on with the Artificial intelligence while the third core could possible calculate the graphic data. In this best case scenario you have to realise that the core number two and three would always have to wait for the core number one to finish its job and pass the job to the cores two and three. In this concept there is absolutely no place for quad core as games are non parallel applications. A game developer expert said that you can use the core number four to stream and load the data in the game and this is what the guys at Remedy did at IDF quad core demonstration. But this takes time and money and it is not commonly embraced by developers.

Game developers are in the dawn of dual core programming and now all the sudden AMD and Intel wants them to go quad core. For the time being Quad cores are good for rendering and serves but not for games.

So if you want to play games, you can forget about quad cores, you simply don’t need them and can gain just marginal performance out of them. Give the developers some time and this might change, but we are talking quarters not months.
Zvýraznil jsem nejdůležitější část. To docela mění zde nastolený směr diskuze - zjevně nebude problém zatížit jedno jádro výpočtem fyziky a kolizí, potíž bude v tom, že chceme-li, aby tato fyzika probíhala realtime (tj. aby například jedno auto neprojelo celé druhým a až pak byla zjištěna kolize), musí být fyzika spočítána hodně rychle, protože se jedná o sekvenční záležitost. A je zřejmě jasné, že když data musíme překopírovat z jednoho CPU do druhého, může DC dokonce i zpomalovat výpočet.

Možná by to šlo vyřešit tak, že jedno jádro bude počítat kolize a fyziku pro jeden frame dopředu, zatímco další jádra aktuální frame. To ale bude docela potíž z hlediska synchronizace a taky tam bude určité zpoždění reakcí na uživatelům vstup (čili zdaleka to nebude optimální).