windows 2008 speed boost

[ricki]

Hi

 

Do you have a windows 2008 and windows 2008 r2 server. If you do please can you go to and download the correct version from here CPUID - System & hardware benchmark, monitoring, reporting for your server and run it.

 

Now go into control panel and check that the server is set to high performance plan. We did it on our servers and its doubled the core speed.

 

I think balanced is the default which is not good for servers.

 

Please can I thank Andrew from Stone for this tip.

 

Richard

[andydis]

Degraded overall performance on Windows Server 2008 R2

 

have a read through this ricki

[Guest TheLibrarian]

This leaves me speechless and feeling like I should repeatedly bang my head against a wall until the lights go out forever.

[SYNACK]

I am reasonably certain that this is just intel speedstep and its derivitaves, the clock speed is dropped when the computer is not doing much to save power and produce less heat. When the work load ramps up so does the clock speed so the boost from having them runing at top speed all the time reagardless of load is probably very small.

[jamesfed]

Doesn’t setting it to high performance turn off core parking (quite a useful power saving feature) as well?

I’ve got all of our VDI servers set to high performance but our ‘core servers’ all run under balanced.

 

If you have a HP server (and I would imagine others as well) there are plenty of other options in the BIOS as well for turning on the higher performance modes (again we use them for our VDI servers only).

[cpjitservices]

Would it make much of a difference if I changed ours to "High performance", I have an IBM Virtual Server running VMWare with all our core servers in it, If I change them to High performance will I see a benefit ?

[SYNACK]

Would it make much of a difference if I changed ours to "High performance", I have an IBM Virtual Server running VMWare with all our core servers in it, If I change them to High performance will I see a benefit ?

 

Unlikely, the speed 'loss' is mainly in ultra low latency stuff so if you have a thread running that is not hogging CPU cycles but would benifit from getting the events through a bit quicker. As the CPU load would be low the speed would not kick up meaning that those single operations would be run at a lower clock rate making them take a very tiny bit longer. The other speed constraint is when the load kicks up really quickly as you have a whole clock cycle or two to ramp up the core speed.

 

In real terms for anything but specialist loads you are probably not going to notice. You will notice the electricity usage increase though.