Oh Brother, What betid to mine Haswell 4770? - Page 6

Mark Rose · 2014-10-08, 18:53

Quote:

Originally Posted by petrw1

I hope not. It is a brand new PC at a friends work place.

I am prone to believe it is just a very poor setup.
That is, akin to a Lamborghini CPU Chip with Ford Fiesta RAM.

A Ford Fiesta ST is a nice car :)

kladner · 2014-10-08, 19:33

Quote:

Would you be kind to post some pictures of your BIOS settings?

I wonder if this is possible on a remote system. Can a EUFI system make BIOS settings accessible to the Borgmeister?

pinhodecarlos · 2014-10-08, 20:12

Quote:

Originally Posted by kladner

I wonder if this is possible on a remote system. Can a EUFI system make BIOS settings accessible to the Borgmeister?

I didn't know it was a remote machine. Just ask your friend to take some pictures with a digital camera. Also take a snap of windows manager, we want to see which services are on and off. On my laptop cruncher only 40 services on, the rest is off including windows updates, windows searcher, NET Framework, etc...off the ones which consume a little of cpu. (list services that are automatic on startup)

petrw1 · 2014-10-10, 05:28

Quote:

Originally Posted by kracker

Well, what I really meant was for you to post the log of Prime95's benchmark(in results.txt I think after it's finished)

Very little gain running more than 1 core....
I cut out the Hyperthreaded lines to stay under 10000 characters.
At the very bottom I am seeing timing for 3584K almost exactly what I was actually seeing. They come close to nullifying all cores after the first.

Code:

Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
CPU speed: 3392.39 MHz, 4 hyperthreaded cores
CPU features: Prefetch, SSE, SSE2, SSE4, AVX, AVX2, FMA
L1 cache size: 32 KB
L2 cache size: 256 KB, L3 cache size: 8 MB
L1 cache line size: 64 bytes
L2 cache line size: 64 bytes
TLBS: 64
Prime95 64-bit version 28.5, RdtscTiming=1
Best time for 1024K FFT length: 4.316 ms., avg: 4.365 ms.
Best time for 1280K FFT length: 5.955 ms., avg: 7.817 ms.
Best time for 1536K FFT length: 7.514 ms., avg: 7.606 ms.
Best time for 1792K FFT length: 9.178 ms., avg: 9.232 ms.
Best time for 2048K FFT length: 10.764 ms., avg: 10.803 ms.
Best time for 2560K FFT length: 13.936 ms., avg: 14.004 ms.
Best time for 3072K FFT length: 16.882 ms., avg: 16.940 ms.
Best time for 3584K FFT length: 20.248 ms., avg: 20.325 ms.
Best time for 4096K FFT length: 23.207 ms., avg: 23.296 ms.
Best time for 5120K FFT length: 29.450 ms., avg: 31.504 ms.
Best time for 6144K FFT length: 35.581 ms., avg: 35.686 ms.
Best time for 7168K FFT length: 42.121 ms., avg: 43.570 ms.
Best time for 8192K FFT length: 49.889 ms., avg: 53.093 ms.
Timing FFTs using 2 threads on 1 physical CPU.
Best time for 1024K FFT length: 4.619 ms., avg: 7.095 ms.
Best time for 1280K FFT length: 6.279 ms., avg: 6.588 ms.
Best time for 1536K FFT length: 7.950 ms., avg: 12.200 ms.
Best time for 1792K FFT length: 9.690 ms., avg: 10.387 ms.
Best time for 2048K FFT length: 11.176 ms., avg: 12.600 ms.
Best time for 2560K FFT length: 14.717 ms., avg: 17.455 ms.
Best time for 3072K FFT length: 17.774 ms., avg: 18.123 ms.
Best time for 3584K FFT length: 20.664 ms., avg: 20.921 ms.
Best time for 4096K FFT length: 24.266 ms., avg: 24.808 ms.
Best time for 5120K FFT length: 30.842 ms., avg: 32.873 ms.
Best time for 6144K FFT length: 37.197 ms., avg: 38.001 ms.
Best time for 7168K FFT length: 43.322 ms., avg: 44.531 ms.
Best time for 8192K FFT length: 51.229 ms., avg: 51.685 ms.
Timing FFTs using 2 threads on 2 physical CPUs.
Best time for 1024K FFT length: 2.561 ms., avg: 2.654 ms.
Best time for 1280K FFT length: 4.102 ms., avg: 5.561 ms.
Best time for 1536K FFT length: 5.307 ms., avg: 5.794 ms.
Best time for 1792K FFT length: 6.667 ms., avg: 7.568 ms.
Best time for 2048K FFT length: 8.151 ms., avg: 8.493 ms.
Best time for 2560K FFT length: 10.508 ms., avg: 10.574 ms.
Best time for 3072K FFT length: 13.018 ms., avg: 13.196 ms.
Best time for 3584K FFT length: 15.140 ms., avg: 15.296 ms.
Best time for 4096K FFT length: 17.679 ms., avg: 18.545 ms.
Best time for 5120K FFT length: 22.282 ms., avg: 22.396 ms.
Best time for 6144K FFT length: 26.889 ms., avg: 28.809 ms.
Best time for 7168K FFT length: 32.132 ms., avg: 33.696 ms.
Best time for 8192K FFT length: 37.879 ms., avg: 38.186 ms.
Timing FFTs using 3 threads on 3 physical CPUs.
Best time for 1024K FFT length: 2.235 ms., avg: 2.450 ms.
Best time for 1280K FFT length: 3.710 ms., avg: 5.687 ms.
Best time for 1536K FFT length: 5.045 ms., avg: 5.331 ms.
Best time for 1792K FFT length: 6.458 ms., avg: 7.982 ms.
Best time for 2048K FFT length: 7.901 ms., avg: 8.435 ms.
Best time for 2560K FFT length: 10.202 ms., avg: 11.442 ms.
Best time for 3072K FFT length: 13.207 ms., avg: 13.826 ms.
Best time for 3584K FFT length: 14.804 ms., avg: 16.189 ms.
Best time for 4096K FFT length: 17.347 ms., avg: 19.702 ms.
Best time for 5120K FFT length: 21.842 ms., avg: 22.895 ms.
Best time for 6144K FFT length: 26.374 ms., avg: 27.837 ms.
Best time for 7168K FFT length: 30.957 ms., avg: 31.961 ms.
Best time for 8192K FFT length: 37.411 ms., avg: 38.285 ms.
Timing FFTs using 4 threads on 4 physical CPUs.
Best time for 1024K FFT length: 1.876 ms., avg: 1.986 ms.
Best time for 1280K FFT length: 3.710 ms., avg: 5.285 ms.
Best time for 1536K FFT length: 5.165 ms., avg: 5.856 ms.
Best time for 1792K FFT length: 6.548 ms., avg: 11.305 ms.
Best time for 2048K FFT length: 7.919 ms., avg: 8.049 ms.
Best time for 2560K FFT length: 10.321 ms., avg: 10.382 ms.
Best time for 3072K FFT length: 12.952 ms., avg: 13.039 ms.
Best time for 3584K FFT length: 15.076 ms., avg: 17.847 ms.
Best time for 4096K FFT length: 17.652 ms., avg: 17.917 ms.
Best time for 5120K FFT length: 22.523 ms., avg: 23.260 ms.
Best time for 6144K FFT length: 26.981 ms., avg: 27.493 ms.
Best time for 7168K FFT length: 31.531 ms., avg: 31.758 ms.
Best time for 8192K FFT length: 37.925 ms., avg: 39.585 ms.
Timing FFTs using 8 threads on 4 physical CPUs.
Best time for 1024K FFT length: 2.405 ms., avg: 2.651 ms.
Best time for 1280K FFT length: 3.778 ms., avg: 3.913 ms.
Best time for 1536K FFT length: 5.284 ms., avg: 5.867 ms.
Best time for 1792K FFT length: 6.808 ms., avg: 7.622 ms.
Best time for 2048K FFT length: 8.152 ms., avg: 8.698 ms.
Best time for 2560K FFT length: 10.570 ms., avg: 11.091 ms.
Best time for 3072K FFT length: 13.206 ms., avg: 13.439 ms.
Best time for 3584K FFT length: 15.440 ms., avg: 15.906 ms.
Best time for 4096K FFT length: 18.105 ms., avg: 18.417 ms.
Best time for 5120K FFT length: 22.407 ms., avg: 23.024 ms.
Best time for 6144K FFT length: 27.319 ms., avg: 27.660 ms.
Best time for 7168K FFT length: 31.856 ms., avg: 32.639 ms.
Best time for 8192K FFT length: 38.538 ms., avg: 39.446 ms.

Timings for 1024K FFT length (1 cpu, 1 worker):  4.42 ms.  Throughput: 226.34 iter/sec.
Timings for 1024K FFT length (2 cpus, 2 workers):  8.27,  8.17 ms.  Throughput: 243.41 iter/sec.
Timings for 1024K FFT length (3 cpus, 3 workers): 12.92, 12.75, 12.68 ms.  Throughput: 234.71 iter/sec.
Timings for 1024K FFT length (4 cpus, 4 workers): 18.66, 18.15, 17.97, 17.44 ms.  Throughput: 221.68 iter/sec.
Timings for 1280K FFT length (1 cpu, 1 worker):  6.12 ms.  Throughput: 163.45 iter/sec.
Timings for 1280K FFT length (2 cpus, 2 workers): 10.85, 10.72 ms.  Throughput: 185.51 iter/sec.
Timings for 1280K FFT length (3 cpus, 3 workers): 16.60, 16.23, 16.03 ms.  Throughput: 184.22 iter/sec.
Timings for 1280K FFT length (4 cpus, 4 workers): 22.92, 22.73, 22.49, 22.68 ms.  Throughput: 176.18 iter/sec.
Timings for 1536K FFT length (1 cpu, 1 worker):  7.86 ms.  Throughput: 127.22 iter/sec.
Timings for 1536K FFT length (2 cpus, 2 workers): 13.15, 13.07 ms.  Throughput: 152.59 iter/sec.
Timings for 1536K FFT length (3 cpus, 3 workers): 20.14, 19.87, 19.54 ms.  Throughput: 151.17 iter/sec.
Timings for 1536K FFT length (4 cpus, 4 workers): 32.81, 27.20, 27.11, 26.50 ms.  Throughput: 141.87 iter/sec.
Timings for 1792K FFT length (1 cpu, 1 worker):  9.30 ms.  Throughput: 107.48 iter/sec.
Timings for 1792K FFT length (2 cpus, 2 workers): 15.39, 15.27 ms.  Throughput: 130.44 iter/sec.
Timings for 1792K FFT length (3 cpus, 3 workers): 23.09, 22.71, 22.74 ms.  Throughput: 131.31 iter/sec.
Timings for 1792K FFT length (4 cpus, 4 workers): 35.02, 32.56, 32.56, 32.20 ms.  Throughput: 121.04 iter/sec.
Timings for 2048K FFT length (1 cpu, 1 worker): 11.00 ms.  Throughput: 90.89 iter/sec.
Timings for 2048K FFT length (2 cpus, 2 workers): 18.12, 17.90 ms.  Throughput: 111.06 iter/sec.
Timings for 2048K FFT length (3 cpus, 3 workers): 27.46, 26.76, 26.45 ms.  Throughput: 111.59 iter/sec.
Timings for 2048K FFT length (4 cpus, 4 workers): 43.68, 35.49, 35.52, 35.25 ms.  Throughput: 107.60 iter/sec.
Timings for 2560K FFT length (1 cpu, 1 worker): 14.16 ms.  Throughput: 70.62 iter/sec.
Timings for 2560K FFT length (2 cpus, 2 workers): 22.59, 22.30 ms.  Throughput: 89.12 iter/sec.
Timings for 2560K FFT length (3 cpus, 3 workers): 34.03, 33.28, 33.39 ms.  Throughput: 89.39 iter/sec.
Timings for 2560K FFT length (4 cpus, 4 workers): 45.87, 45.14, 44.72, 44.20 ms.  Throughput: 88.94 iter/sec.
Timings for 3072K FFT length (1 cpu, 1 worker): 17.13 ms.  Throughput: 58.39 iter/sec.
Timings for 3072K FFT length (2 cpus, 2 workers): 29.53, 27.82 ms.  Throughput: 69.81 iter/sec.
Timings for 3072K FFT length (3 cpus, 3 workers): 42.69, 41.27, 41.13 ms.  Throughput: 71.97 iter/sec.
Timings for 3072K FFT length (4 cpus, 4 workers): 59.33, 57.18, 57.36, 57.09 ms.  Throughput: 69.30 iter/sec.
Timings for 3584K FFT length (1 cpu, 1 worker): 20.60 ms.  Throughput: 48.55 iter/sec.
Timings for 3584K FFT length (2 cpus, 2 workers): 32.28, 31.86 ms.  Throughput: 62.37 iter/sec.
Timings for 3584K FFT length (3 cpus, 3 workers): 49.15, 47.99, 46.11 ms.  Throughput: 62.87 iter/sec.
Timings for 3584K FFT length (4 cpus, 4 workers): 68.90, 64.68, 65.81, 64.67 ms.  Throughput: 60.63 iter/sec.

garo · 2014-10-10, 06:23

Can you install CoreTemp and get temps for idle, 1 thread, 2 threads and so on?

axn · 2014-10-10, 08:22

Quote:

Originally Posted by petrw1

Very little gain running more than 1 core....
I cut out the Hyperthreaded lines to stay under 10000 characters.
At the very bottom I am seeing timing for 3584K almost exactly what I was actually seeing. They come close to nullifying all cores after the first.

Actually, looking at the numbers, there might be a way to greatly boost your throughput. Try running 1 LL test using 4 threads (or even 3 threads). That might actually give you more throughput than running 2 LLs x 1 thread each (hopefully, closer to 3 LLs).

EDIT:- Not really. So based on actual numbers,

Code:

Best time for 3584K FFT length: 20.248 ms., avg: 20.325 ms.
Timing FFTs using 2 threads on 1 physical CPU.
Best time for 3584K FFT length: 20.664 ms., avg: 20.921 ms.
Timing FFTs using 2 threads on 2 physical CPUs.
Best time for 3584K FFT length: 15.140 ms., avg: 15.296 ms.
Timing FFTs using 3 threads on 3 physical CPUs.
Best time for 3584K FFT length: 14.804 ms., avg: 16.189 ms.
Timing FFTs using 4 threads on 4 physical CPUs.
Best time for 3584K FFT length: 15.076 ms., avg: 17.847 ms.
Timing FFTs using 8 threads on 4 physical CPUs.
Best time for 3584K FFT length: 15.440 ms., avg: 15.906 ms.

1 LL 2 threads gives a throughput of 1000/15.3 = 65.3 iter/sec, which is only marginally better than 2 LL x 1 thread (62.4 iter/sec). Nonetheless, that is probably the way to go. While 3 threads have better "best-case", it's average case is really bad.

axn · 2014-10-10, 08:52

Quote:

Originally Posted by garo

Can you install CoreTemp and get temps for idle, 1 thread, 2 threads and so on?

Code:

Timing FFTs using 4 threads on 4 physical CPUs.
Best time for 1024K FFT length: 1.876 ms., avg: 1.986 ms.
Timings for 1024K FFT length (4 cpus, 4 workers): 18.66, 18.15, 17.97, 17.44 ms.  Throughput: 221.68 iter/sec.

These three lines effectively demolish any temp throttling hypotheses. When the entire FFT fits within the cache (or nearly so), you get a thruput of more than twice that of the 4 test case.

petrw1 · 2014-10-10, 16:51

Quote:

Originally Posted by axn

Actually, looking at the numbers, there might be a way to greatly boost your throughput. Try running 1 LL test using 4 threads (or even 3 threads). That might actually give you more throughput than running 2 LLs x 1 thread each (hopefully, closer to 3 LLs).

EDIT:- Not really. So based on actual numbers,

Code:

Best time for 3584K FFT length: 20.248 ms., avg: 20.325 ms.
Timing FFTs using 2 threads on 1 physical CPU.
Best time for 3584K FFT length: 20.664 ms., avg: 20.921 ms.
Timing FFTs using 2 threads on 2 physical CPUs.
Best time for 3584K FFT length: 15.140 ms., avg: 15.296 ms.
Timing FFTs using 3 threads on 3 physical CPUs.
Best time for 3584K FFT length: 14.804 ms., avg: 16.189 ms.
Timing FFTs using 4 threads on 4 physical CPUs.
Best time for 3584K FFT length: 15.076 ms., avg: 17.847 ms.
Timing FFTs using 8 threads on 4 physical CPUs.
Best time for 3584K FFT length: 15.440 ms., avg: 15.906 ms.

1 LL 2 threads gives a throughput of 1000/15.3 = 65.3 iter/sec, which is only marginally better than 2 LL x 1 thread (62.4 iter/sec). Nonetheless, that is probably the way to go. While 3 threads have better "best-case", it's average case is really bad.

Or sadly is the best overall gimps benefit to run 1 LL at 20ms for 3548fft and tf or ecm on the other 3 cores. Currently testing with # LL and 2 ECM

kracker · 2014-10-10, 18:04

It's either temps or memory by now...

petrw1 · 2014-10-10, 20:01

Quote:

Originally Posted by petrw1

Or sadly is the best overall gimps benefit to run 1 LL at 20ms for 3548fft and tf or ecm on the other 3 cores. Currently testing with # LL and 2 ECM

Oops should say 2 LL and 2 ECM (Small).
I already know that adding 2 TF does NOT impact the LL time by more than a percent or two. I was doing 50xxx TF to 61,62 bits on 2 cores when this PC first turned up. These assignments were giving me 7 GhzDays / Day / Core.

I find that TF assignments for bit levels below 65 are quite generous. So I know that if I let it do the current TF assignments that PrimeNet would hand out (66 - 72 bits) it would not be quite that productive. But it will be a LOT more than 2 ... see next point.

I have noted so far that it completes 2 ECM (one each from core #1 and #3) in 4:30. That works out to 2 GhzDays / Day / Core. I have 800MB RAM of the 4000MB total allocated. I think this should be enough for ECM Small even if both are in Stage 2.

I need a day or two to determine if this slows down the LL workers.

If it does cause a LL slowdown I'll try 1 TF and 1 ECM.

kracker · 2014-10-10, 21:00

Have you checked the temperatures yet?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Computer isn't mine...	CuriousKit	PrimeNet	25	2016-06-02 05:44
gpu72 site - exp 78227507 credited but not mine?	dh1	GPU to 72	1	2015-11-29 14:03
Your end or mine?	davieddy	Lounge	0	2011-12-11 11:31
Hey brother, can you help a friend in need?	petrw1	Math	3	2008-03-30 14:20
some questions of mine, in general	jerico2day	Software	5	2005-03-30 09:19

2014-10-10, 06:23	#60
garo Aug 2002 Termonfeckin, IE ACC₁₆ Posts	Can you install CoreTemp and get temps for idle, 1 thread, 2 threads and so on?

2014-10-10, 18:04	#64
kracker "Mr. Meeseeks" Jan 2012 California, USA 2³×271 Posts	It's either temps or memory by now...

2014-10-10, 21:00	#66
kracker "Mr. Meeseeks" Jan 2012 California, USA 878₁₆ Posts	Have you checked the temperatures yet?