Archived from groups: microsoft.public.windowsxp.general (More info?)
We recently got two new PCs (P4, Intel 865, FX5200 dual monitor, XP Pro) for
software development. After loading VS2003 and our project's code on the new
machines, we noticed several performance problems with the VS IDE and with
our application. Our app., which worked fine on our older, slower P4 running
Win2K, runs extremely slow on the new PC, 5-15 seconds to react to mouse
clicks, even longer to redraw the main window after resizing, etc. The VS
IDE just seems to bog down at times. This happens on both new PCs.
After much wondering and head scratching, we disabled hyperthreading in the
BIOS and everything worked fine.
As near as we can tell, the OS is detects when hyperthreading is enabled
(two processors shown in Device Manager), but our app just doesn't seem to
run right unless the hyperthreading is disable. BTW, the app seems to run
OK on a PC with HT and XP Home.
Google and MSDN search didn't turn up anything. We need to find a solution
so our customers on XP don't have to change their BIOS to run our software.
Anybody run into anything like this? Any suggestions?
Steve
We recently got two new PCs (P4, Intel 865, FX5200 dual monitor, XP Pro) for
software development. After loading VS2003 and our project's code on the new
machines, we noticed several performance problems with the VS IDE and with
our application. Our app., which worked fine on our older, slower P4 running
Win2K, runs extremely slow on the new PC, 5-15 seconds to react to mouse
clicks, even longer to redraw the main window after resizing, etc. The VS
IDE just seems to bog down at times. This happens on both new PCs.
After much wondering and head scratching, we disabled hyperthreading in the
BIOS and everything worked fine.
As near as we can tell, the OS is detects when hyperthreading is enabled
(two processors shown in Device Manager), but our app just doesn't seem to
run right unless the hyperthreading is disable. BTW, the app seems to run
OK on a PC with HT and XP Home.
Google and MSDN search didn't turn up anything. We need to find a solution
so our customers on XP don't have to change their BIOS to run our software.
Anybody run into anything like this? Any suggestions?
Steve