Workload in core 0 and core 1

[pmr]

Well, I´ve seen complaints of several C2D users telling that all the work, in single threaded apps, is being done by core 0 of the cpu, while core 1 is just sitting there.
But in my case, I always see the workload being splited by the two cores. What in hell is happening?
Is everything ok?
Do I need a patch?
Do they need a patch?

(Super pi 1M is done in 26 secs and everything seems to run fine)

Thanks.

 

[ajfink]

You're complaining that your dual-core CPU is using both cores?

Let's see what we find wrong with this issue.

 

[pmr]

I know my english is not pefect, but...(and now read this very slowly) did you read any complaints from me about the cpu using the two cores?
Just asking if is this the normal way to work, or the other way.

 

[TechnologyCoordinator]

In some cases the splitting of work is good. In other cases it is bad. Keep in mind this has nothing to do with what processor you have, but rather the operating system that manages what work is performed and where.

For must purposes, the splitting of work is good. However, in some cases, such as games, the splitting of work (taking the same thread and bouncing it between cores) is not good. For example, I just upgraded to dual core and noticed stuttering in CounterStrike:Source. This stuttering issue was caused by the single-threaded CounterStrike:Source being bounced between the two cores. When I set the affinity of CouterStrike:Source(hl2.exe) to only run on core 1 my stuttering issue went away and performance increased dramatically.

Until software catches up with the hardware we will have to worry about this issue. Keep in mind that we are buying dual-core systems but then putting all our old, single core software back on it and wondering why it doesn't work to the hardware's potential.

 

[pmr]

That´s nice. I think I´m going to try the affinity thing in some single threaded apps.

Thanks

 

[rodney_ws]

Yeah, Neverwinter Nights has a HUGE issue with dual core systems... the game runs like lightning (and not in a good way) on a dual core system... and I too had to set the application's affinity to remedy the problem.

Going forward I don't think any applications (even ones that are single-threaded) will exhibit that behavior... at least none that I've seen to date.

 

[Doughbuy]

Hopefully Vista will fix this....

 

[rodney_ws]

I think software developers already have.