Dual Core processors and WinXP

F

frankyk

Gawd
Joined
Jan 30, 2004
Messages
891
Why is it that when say PowerDVD or IE or any program in general screws up that my computer turns into a slow piece of crap? Isn't the dual core processor supposed to take the crap that's accessing the problem and at least have one core work on something else?
 
It's generating an error report and using your hard drive to dump the memory from the program, generally.

Your second core isn't there to make your hard drive faster, or to make coredumps go faster.
 
^^^hahaha. nice one :)

Looks like this guy fell for the '2 cores = twice as fast' marketing :)
 
i thought it was supposed to work another core when one cpu is going at another 100%? wtf.
 
frankyk said:
i thought it was supposed to work another core when one cpu is going at another 100%? wtf.
Click to expand...

Only if the program is specifically written to be multi-threaded. Otherwise it'll just make use of one core.

If you run another program, the OS will likely assign it to your free core. Or you can use a program like SMP SeeSaw to isolate processes on a single core/cpu and offload everything else to the free core.
 
frankyk said:
Why is it that when say PowerDVD or IE or any program in general screws up that my computer turns into a slow piece of crap? Isn't the dual core processor supposed to take the crap that's accessing the problem and at least have one core work on something else?
Click to expand...

Does it do it for a long period of time? Or is it a short term thing?


The OS is supposed to schedule threads appropriately based on feedback queue. But if an OS subsystem (which can also be in use by any/everything else running) in use by either of those is gimped because of those crashes, then all bets are off.

I'd be more concerned about figuring out why your PowerDVD and IE are crashing.
 
You must log in or register to reply here.
Back
Top