I have noticed this in the past, but it is massive on my new work machine. Although the machine has four processors, when one is working full-out it takes forever to get the machine's attention.
It's an HP Elitebook 8560w, with 4 cores running at - whoops, it's idle now and they are throttled down to 798 Mhz. Rated at 2 Ghz. 8 GB of dual-channelDDR3 at 666 Mhz, FSB:RAM ratio of 1:5. Running 32-bit XP until the company certifies 64-bit Win7 for use.
When I run a massive single-thread computation, like recompiling our main project and running all of the Junit tests, I see one CPU running flat-out and the others nearly idle. But if I try to switch tasks, or hit ctl-alt-delete and open the task manager, it can take up to ten seconds to get its attention. Is this a normal behavior for XP? Can you think of any reason? There is a lot of company security stuff running in the background, but it's usually quiet, and I never have this problem unless one core is being pushed full-out.
If it makes a difference, I disabled Hyperthreading. I haven't yet tried the experiment of re-enabling it.
Thanks.
It's an HP Elitebook 8560w, with 4 cores running at - whoops, it's idle now and they are throttled down to 798 Mhz. Rated at 2 Ghz. 8 GB of dual-channelDDR3 at 666 Mhz, FSB:RAM ratio of 1:5. Running 32-bit XP until the company certifies 64-bit Win7 for use.
When I run a massive single-thread computation, like recompiling our main project and running all of the Junit tests, I see one CPU running flat-out and the others nearly idle. But if I try to switch tasks, or hit ctl-alt-delete and open the task manager, it can take up to ten seconds to get its attention. Is this a normal behavior for XP? Can you think of any reason? There is a lot of company security stuff running in the background, but it's usually quiet, and I never have this problem unless one core is being pushed full-out.
If it makes a difference, I disabled Hyperthreading. I haven't yet tried the experiment of re-enabling it.
Thanks.