![]() |
|
|
#89 |
|
"Jason Lynch"
Jun 2008
Spokane, WA
138 Posts |
I'm getting really inconsistent performance on my Threadripper PRO 3955WX (16 cores) running Windows 10 for Workstations. I've only ever used 30.7 builds on this machine, so I don't have any earlier points of comparison (but will certainly test earlier versions if it would matter).
I'm using one worker with 8 threads. Recently, when doing some double checks, it would bounce between either ~2.1ms/iter or ~2.8ms/iter (with no other processes heavily using CPU). Once it was in a particular range, it wouldn't change during a run, but might change modalities after an auto-benchmark or manually stopping/starting. (Though I haven't seen the faster mode since the most recent boot which included a BIOS update and a Windows update.) If other programs were using the CPU, those would slow incrementally (2.1 to maybe as low as 2.5 and 2.8 to maybe 3.2), but there were two clear patterns. Manually assigning affinities in local.txt did help to some extent as well. Now, having moved on to a larger PRP test in the 110M range, a throughput test on the same settings suggested ~6.6ms/iter, but the test itself was getting ~8.7ms/iter. After restarting the test after removing my Affinity= line, the test now decreased to ~8.0ms/iter, but either I'm misunderstanding the benchmark or there's still something strange going on. Anyway, if anyone has any ideas or can explain what I'm missing, I'd be all ears. Don't seem to have any similar issues on my 3700X or Threadripper 3960X, but both of those machines are running Linux. |
|
|
|
|
|
#90 |
|
P90 years forever!
Aug 2002
Yeehaw, FL
17×487 Posts |
Build 7 is available. Build 6 does not exist (except for Kruoli).
There is still at least one bug remaining. Running multiple ECM workers can crash with either an out-of-memory event or a restarting with new memory settings event. I've been running for a week under the debugger without any luck. Kruoli has seen one crash in that time. |
|
|
|
|
|
#91 |
|
Dec 2007
112 Posts |
all latest prime95 will fail to run with core cycler .....
|
|
|
|
|
|
#92 | |
|
Nov 2014
3·13 Posts |
Quote:
|
|
|
|
|
|
|
#93 |
|
P90 years forever!
Aug 2002
Yeehaw, FL
17×487 Posts |
|
|
|
|
|
|
#94 |
|
"Oliver"
Sep 2017
Porta Westfalica, DE
110011000012 Posts |
Wavefront P-1, In build 5, when day and night memory settings are different, stage 2 cannot be resumed from the larger memory part:
Code:
[Work thread Oct 29 06:19] M107021149 stage 2 is 45.45% complete. Time: 1957.403 sec. [Work thread Oct 29 06:52] M107021149 stage 2 is 53.92% complete. Time: 1969.442 sec. [Work thread Oct 29 07:00] Restarting worker with new memory settings. [Work thread Oct 29 07:00] Optimal P-1 factoring of M107021149 using up to 24576MB of memory. [Work thread Oct 29 07:00] Assuming no factors below 2^76 and 4 primality tests saved if a factor is found. [Work thread Oct 29 07:00] Optimal bounds are B1=1729000, B2=94551000 [Work thread Oct 29 07:00] Chance of finding a factor is an estimated 5.53% [Work thread Oct 29 07:00] [Work thread Oct 29 07:00] Using FMA3 FFT length 5760K, Pass1=1536, Pass2=3840, clm=1, 8 threads [Work thread Oct 29 07:00] D: 330, relative primes: 354, stage 2 primes: 5335022, pair%=92.41 [Work thread Oct 29 07:00] Using 16371MB of memory. [Work thread Oct 29 07:00] Stage 2 init complete. 848 transforms. Time: 9.439 sec. [Work thread Oct 29 07:00] M107021149 stage 2 is 0.00% complete. [Work thread Oct 29 07:32] M107021149 stage 2 is 8.20% complete. Time: 1901.034 sec. [Work thread Oct 29 08:03] M107021149 stage 2 is 16.51% complete. Time: 1903.386 sec. [Work thread Oct 29 08:35] M107021149 stage 2 is 24.89% complete. Time: 1901.938 sec. [Work thread Oct 29 09:07] M107021149 stage 2 is 33.34% complete. Time: 1902.549 sec. |
|
|
|
|
|
#95 |
|
P90 years forever!
Aug 2002
Yeehaw, FL
205716 Posts |
|
|
|
|
|
|
#96 | |
|
"Jason Lynch"
Jun 2008
Spokane, WA
11 Posts |
Quote:
That said, when using only 8 of the available 16 cores, the affinities chosen by Prime95 seem to be suboptimal (which might be expected, given that I think I read somewhere that it's optimized assuming all cores are used). (The default selection on a 5760K CERT run gave about 4.7ms/iter, whereas a manual Affinity setting of 0,4,8,12,16,20,24,28 gave me 3.9ms/iter). I have no idea why that pattern would be better, that was just the fastest one I found. Last fiddled with by Aexoden on 2021-10-29 at 21:32 |
|
|
|
|
|
|
#97 |
|
Oct 2021
U. S. / New York, NY
2·3·52 Posts |
Probably a stupid question:
When one is using the cert range controls provided in undoc.txt (Cert[Min|Max]Exponent), do you need to add both lines for the functionality to work, or are you fine to add only one or the other? |
|
|
|
|
|
#98 |
|
P90 years forever!
Aug 2002
Yeehaw, FL
827910 Posts |
|
|
|
|
|
|
#99 | |
|
Nov 2020
Oklahoma, USA
22 Posts |
Quote:
I only have CertMinExponent=0 and have never noticed any issues. |
|
|
|
|