This has been posted before - and in fact it's almost common knowledge - but it bit me again today and so it perhaps bears repeating:
If you have a Windows server, putting the OS and BIOS into anything other than "high performance" mode will destroy performance.
I have been running a pile of ETL on my DL585 G7 this week - around 60 billion rows so far. CPU utilization is nil - around 5% - and the disk IO barely registers, and yet I'm still able to push data rows through a 50-step ETL flow with 7 lookup steps at a rate of 50K rows/second. Then I noticed that I was in "balanced" performance mode in the Windows control panel. I switched to "high performance" mode and the ETL load rate instantly shot up to 120K rows/second. Power consumption went from 560 watts to 585 watts.
So basically the "power saving" feature was reducing power consumption by 4% and in return reducing throughput by 60%. That's a painful trade-off!
If you have a Windows server, putting the OS and BIOS into anything other than "high performance" mode will destroy performance.
I have been running a pile of ETL on my DL585 G7 this week - around 60 billion rows so far. CPU utilization is nil - around 5% - and the disk IO barely registers, and yet I'm still able to push data rows through a 50-step ETL flow with 7 lookup steps at a rate of 50K rows/second. Then I noticed that I was in "balanced" performance mode in the Windows control panel. I switched to "high performance" mode and the ETL load rate instantly shot up to 120K rows/second. Power consumption went from 560 watts to 585 watts.
So basically the "power saving" feature was reducing power consumption by 4% and in return reducing throughput by 60%. That's a painful trade-off!