6-core Sandy Bridge test case

TObject · 2013-11-21, 21:21

In case anyone is interested, I just measured the differences in iteration times running Prime95 with five workers, versus five workers plus one helper thread on the last worker.

The affinity scramble is configured so that each of the Prime95 main or helper workers lands on its own physical core.

What is special about this case is that the computer has a continuously running OpenCL job in the form of a Radeon HD 7790 loaded to almost 100%. The OpenCL does appear to steal quite a few CPU cycles (though in theory it does not have to).

Exponent range: current first time LL front, 60M or so.

Here is the data (iteration times in seconds):

Code:

 FFT   |  5 workers  | 5+1 workers
----------------------------------
3360K  |   0.027     |  0.030
3M     |   0.024     |  0.027
3200K  |   0.025     |  0.028
3200K  |   0.025     |  0.028
3456K  |   0.025     |  0.016
---------------------------------
Average|   0.0258    |  0.0258

Intel Core i7-3930K @ 3.20GHz, Quad Channel Memory (16 GB), Windows64, v27.9, build 1

Nothing is overclocked, though Turbo Boost is on, memory is on Intel standard timing (XMP is off).

The goal of this test was to ensure that giving another core to Prime95 would not slow down overall LL testing progress.

As you can see, the average per worker iteration time is exactly the same in both configurations. Conclusion: for this machine, do not use the sixth core for a Prime95 helper thread.

henryzz · 2013-11-21, 22:17

What speed is your memory? Even with quad channel it is quite possible that 6 cores(possibly 4-5) could max out you memory bandwidth.

TObject · 2013-11-21, 22:38

Quote:

Originally Posted by henryzz

What speed is your memory? Even with quad channel it is quite possible that 6 cores(possibly 4-5) could max out you memory bandwidth.

Last September this computer had originally passed 36 hours of Memtest86 at XMP setting of 1600 MT/s, 9-9-9-24.

A year later, Prime95 started throwing errors and going back to previous save files. I checked the memory – at least two sticks became faulty.

I replaced all memory with a brand new set, and, to be on the safe side, I will not be overclocking memory on this computer anymore.

The current memory speed is 1333 MT/s, 9-9-9-24.

axn · 2013-11-22, 03:13

Quote:

Originally Posted by TObject

As you can see, the average per worker iteration time is exactly the same in both configurations. Conclusion: for this machine, do not use the sixth core for a Prime95 helper thread.

First off, the average from first column is 0.0252, not 0.0258.

However, raw average is not the correct way to do this -- you should be taking harmonic mean. You should calculate the number of iterations per second (1/t), take their average and invert it. When you do that, we end up with average iteration times of 0.0252 and 0.0245 respectively. That makes the second configuration the better one.

danaj · 2013-11-22, 03:38

There are a few 6-core Sandy Bridge results on the Perpetual benchmark thread (3930K, 3960X, 3930K). Most of them seem to show a faster time with 6 CPUs vs. 5. This may be different than what you're looking at however, and are almost certainly on idle computers.

TObject · 2013-11-22, 04:03

Somebody changed the numbers in my original post. Very funny.

TheMawn · 2013-11-22, 06:03

Make sure your RAM is in fact in quad channel. Based on the fact that you know what memtest86+ is and that you know some about frequencies and timings you probably DO know.

If you want, you could clock your cores down 500 - 1000 MHz and re-do the test. If the iteration times go up, you're CPU limited. If they don't, you're RAM limited.

Quad channel at 1333 MHz is going to be pushing it. I've got an i5-3570k @ 4.6 GHz and dual channel 2400 MHz 10-12-12-31 RAM and iteration times go up 20% with the fourth core running. Heavy memory bottleneck.

You've got effectively 2666 MHz of dual channel RAM on six 3.4 (?) GHz cores, so you're roughly in the same ballpark as me. 10% faster memory bandwidth, 50% more cores but I have 33% higher frequency.

TObject · 2013-11-22, 20:01

Thanks for your help, everybody. My original conclusion was wrong. Here is the fixed table

Code:

 FFT   |  5 workers  | 5+1 workers
----------------------------------
3360K  |   0.027     |  0.030
3M     |   0.024     |  0.027
3200K  |   0.025     |  0.028
3200K  |   0.025     |  0.028
3456K  |   0.028     |  0.016
---------------------------------
Average|   0.0258    |  0.0258
GEOMEAN|   0.0258    |  0.0252
HARMEAN|   0.0257    |  0.0245

Iteration times in seconds.

kracker · 2013-11-22, 20:22

Quote:

Originally Posted by TObject

What is special about this case is that the computer has a continuously running OpenCL job in the form of a Radeon HD 7790 loaded to almost 100%. The OpenCL does appear to steal quite a few CPU cycles (though in theory it does not have to).

Just curious, what driver do you have for it?

TObject · 2013-11-22, 20:33

Quote:

Originally Posted by kracker

Just curious, what driver do you have for it?

13-4

kracker · 2013-11-22, 21:29

Quote:

Originally Posted by TObject

13-4

Ah. Above 13-1, there is a cpu "bug". Flooding mfakto out(low priority, etc) will not affect output.

2013-11-21, 21:21	#1
TObject Feb 2012 3⁴×5 Posts	6-core Sandy Bridge test case In case anyone is interested, I just measured the differences in iteration times running Prime95 with five workers, versus five workers plus one helper thread on the last worker. The affinity scramble is configured so that each of the Prime95 main or helper workers lands on its own physical core. What is special about this case is that the computer has a continuously running OpenCL job in the form of a Radeon HD 7790 loaded to almost 100%. The OpenCL does appear to steal quite a few CPU cycles (though in theory it does not have to). Exponent range: current first time LL front, 60M or so. Here is the data (iteration times in seconds): Code: FFT \| 5 workers \| 5+1 workers ---------------------------------- 3360K \| 0.027 \| 0.030 3M \| 0.024 \| 0.027 3200K \| 0.025 \| 0.028 3200K \| 0.025 \| 0.028 3456K \| 0.025 \| 0.016 --------------------------------- Average\| 0.0258 \| 0.0258 Intel Core i7-3930K @ 3.20GHz, Quad Channel Memory (16 GB), Windows64, v27.9, build 1 Nothing is overclocked, though Turbo Boost is on, memory is on Intel standard timing (XMP is off). The goal of this test was to ensure that giving another core to Prime95 would not slow down overall LL testing progress. As you can see, the average per worker iteration time is exactly the same in both configurations. Conclusion: for this machine, do not use the sixth core for a Prime95 helper thread.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
So Sandy Bridge Xeons are now launched	fivemack	Hardware	6	2012-03-14 11:27
Overclocking, Sandy Bridge-E : Don't	firejuggler	Hardware	6	2012-03-08 19:38
2 disabled cores in new Sandy Bridge-E :(	stars10250	Hardware	8	2011-11-16 13:55
Sandy Bridge CPU Usage only 50 percent	dmoran	Software	3	2011-06-14 21:21
Sandy Bridge benchmarks are out.	nucleon	Hardware	0	2011-01-04 11:41

2013-11-21, 22:17	#2
henryzz Just call me Henry "David" Sep 2007 Cambridge (GMT/BST) 16FE₁₆ Posts	What speed is your memory? Even with quad channel it is quite possible that 6 cores(possibly 4-5) could max out you memory bandwidth.

2013-11-22, 03:38	#5
danaj "Dana Jacobsen" Feb 2011 Bangkok, TH 38C₁₆ Posts	There are a few 6-core Sandy Bridge results on the Perpetual benchmark thread (3930K, 3960X, 3930K). Most of them seem to show a faster time with 6 CPUs vs. 5. This may be different than what you're looking at however, and are almost certainly on idle computers.

2013-11-22, 04:03	#6
TObject Feb 2012 3⁴×5 Posts	Somebody changed the numbers in my original post. Very funny.

2013-11-22, 06:03	#7
TheMawn May 2013 East. Always East. 11×157 Posts	Make sure your RAM is in fact in quad channel. Based on the fact that you know what memtest86+ is and that you know some about frequencies and timings you probably DO know. If you want, you could clock your cores down 500 - 1000 MHz and re-do the test. If the iteration times go up, you're CPU limited. If they don't, you're RAM limited. Quad channel at 1333 MHz is going to be pushing it. I've got an i5-3570k @ 4.6 GHz and dual channel 2400 MHz 10-12-12-31 RAM and iteration times go up 20% with the fourth core running. Heavy memory bottleneck. You've got effectively 2666 MHz of dual channel RAM on six 3.4 (?) GHz cores, so you're roughly in the same ballpark as me. 10% faster memory bandwidth, 50% more cores but I have 33% higher frequency.