I have 1 server R610 running Ubuntu with 2 Xeon CPU's X5650 (bought in 2011). and i have 1 R620 running Ubuntu with 2 Xeon E5-2630 CPU's (bought 2013).
I would expect the E5-2630 CPU's to be faster, but i noticed that with the same job it was significant slower. So i started to do a test.
I tested with: sysbench --test=cpu --cpu-max-prime=20000 run This starts a test with 1 thread for a maximum prime number check.
With R610 it lasted 23.47 seconds
With R620 it lasted 32.67 seconds.
I would think the R620 would be a little bit faster then the R610, however it is a lot slower!
I have set the BIOS values as described in this paper:http://i.dell.com/sites/content/shared-content/data-sheets/en/Documents/configuring-low-latency-environments-on-dell-poweredge-12g-servers.pdf
And i upgraded the Bios of the R620 to 2.1.3 (latest version), but no still no improvement.
Difference between the R610 and R620:
R610: Ubuntu 11 - 12 Gb Ram
R620: Ubuntu 12 - 8 Gb Ram
The processes i use (imagemagick) do almost not use memory. The CPU power is all it needs....
What else can i do to improve the CPU speed for the R620. As my program heavily depends on the CPU.
There have been many reports of performance benchmark tools rating older servers as better than our 12th generation servers. This is typically due to new power saving features. Our 12th generation servers are the most power efficient we have released. These power saving features can cause slower performance in some scenarios. For instance, if everything is idled down and you start a benchmark it may come back with bad results because there is a startup delay on increasing the voltage on memory and CPU processing.
To make sure this is the issue I would recommend that you boot into the system BIOS and change the system profile and disable all power saving features. Run your tests again and if they produce the desired results you should adjust the power saving features to meet your needs. I would not recommend leaving all power saving features disabled as it could lead to a dramatic increase in your electric bill. In a single server it may not matter much, but in a datacenter the change could be very significant.
If the issue persists after disabling all power saving features then let me know and we could look into other possibilities.
I just edited my above post to correct a very big typo. "QPI speed, cache, and all prefetching features on the processor should be enabled." Changed disabled to enabled on that line.
And you mention to disable "all power saving features". Which are those exaclty? (before i start making my trip to the datacenter)
If you followed the article that you listed and set to all of the recommended settings then all power saving features would be disabled. For testing purposes turbo boost, C states, advanced memory error correction, and scrubbing/monitoring should be disabled. QPI speed, cache, and all prefetching features on the processor should be enabled.
Yes, if you don't have console access via a remote KVM or iDRAC enterprise then you will need physical access to change BIOS settings.
I see one option disabled which will have a significant impact on performance. The very first option under processor settings for Logical Processor is disabled. This disables hyperthreading on the CPU.
Most newer operating systems are capable of switching between hyperthreading on and off with little or no issues, but please check on your specific version of Ubuntu to make sure there will not be OS corruption when enabling this feature.
Daniel My
12 Elder
•
6204 Posts
3192
0
Posted January 3rd, 2014 13:00
Hello again Marcel
There have been many reports of performance benchmark tools rating older servers as better than our 12th generation servers. This is typically due to new power saving features. Our 12th generation servers are the most power efficient we have released. These power saving features can cause slower performance in some scenarios. For instance, if everything is idled down and you start a benchmark it may come back with bad results because there is a startup delay on increasing the voltage on memory and CPU processing.
To make sure this is the issue I would recommend that you boot into the system BIOS and change the system profile and disable all power saving features. Run your tests again and if they produce the desired results you should adjust the power saving features to meet your needs. I would not recommend leaving all power saving features disabled as it could lead to a dramatic increase in your electric bill. In a single server it may not matter much, but in a datacenter the change could be very significant.
If the issue persists after disabling all power saving features then let me know and we could look into other possibilities.
Thanks