P95 Work Tests @ different lengths

[LOUISSSSS]

I'm currently running some stability tests on my system and noticed that P95 v25.6 runs each work thread @ different lengths. What i mean is

[Feb 28 01:35] Self-test 20K passed!
[Feb 28 01:35] Test 1, 9000 Lucas-Lehmer iterations of M8716289 using FFT length 448K.
[Feb 28 01:39] Test 2, 9000 Lucas-Lehmer iterations of M8716287 using FFT length 448K.
[Feb 28 01:41] Test 3, 9000 Lucas-Lehmer iterations of M8516289 using FFT length 448K.
[Feb 28 01:44] Test 4, 9000 Lucas-Lehmer iterations of M8316287 using FFT length 448K.
[Feb 28 01:46] Test 5, 9000 Lucas-Lehmer iterations of M8257537 using FFT length 448K.
[Feb 28 01:49] Test 6, 9000 Lucas-Lehmer iterations of M8257535 using FFT length 448K.
[Feb 28 01:51] Self-test 448K passed!
[Feb 28 01:51] Test 1, 11000 Lucas-Lehmer iterations of M7471105 using FFT length 384K.
[Feb 28 01:54] Test 2, 11000 Lucas-Lehmer iterations of M7471103 using FFT length 384K.
[Feb 28 01:56] Test 3, 11000 Lucas-Lehmer iterations of M7377889 using FFT length 384K.
[Feb 28 01:59] Test 4, 11000 Lucas-Lehmer iterations of M7277887 using FFT length 384K.
[Feb 28 02:01] Test 5, 11000 Lucas-Lehmer iterations of M7077889 using FFT length 384K.
[Feb 28 02:05] Test 6, 11000 Lucas-Lehmer iterations of M7077887 using FFT length 384K.
[Feb 28 02:07] Self-test 384K passed!

[Feb 28 01:38] Self-test 20K passed!
[Feb 28 01:38] Test 1, 9000 Lucas-Lehmer iterations of M8716289 using FFT length 448K.
[Feb 28 01:41] Test 2, 9000 Lucas-Lehmer iterations of M8716287 using FFT length 448K.
[Feb 28 01:43] Test 3, 9000 Lucas-Lehmer iterations of M8516289 using FFT length 448K.
[Feb 28 01:47] Test 4, 9000 Lucas-Lehmer iterations of M8316287 using FFT length 448K.
[Feb 28 01:49] Test 5, 9000 Lucas-Lehmer iterations of M8257537 using FFT length 448K.
[Feb 28 01:52] Test 6, 9000 Lucas-Lehmer iterations of M8257535 using FFT length 448K.
[Feb 28 01:54] Self-test 448K passed!
[Feb 28 01:54] Test 1, 11000 Lucas-Lehmer iterations of M7471105 using FFT length 384K.
[Feb 28 01:59] Test 2, 11000 Lucas-Lehmer iterations of M7471103 using FFT length 384K.
[Feb 28 02:02] Test 3, 11000 Lucas-Lehmer iterations of M7377889 using FFT length 384K.
[Feb 28 02:05] Test 4, 11000 Lucas-Lehmer iterations of M7277887 using FFT length 384K.
[Feb 28 02:07] Test 5, 11000 Lucas-Lehmer iterations of M7077889 using FFT length 384K.
[Feb 28 02:10] Self-test 384K passed!




Those are just 2 of the 4 of the worker threads, notice that one of the tests finish after "Test 5" and the other after "Test 6" why is that? There are multiple instances of this throughout the few hours i've been running it

 

[lopri]

Because there are other process your CPU have to take care of. Open the Task Manager and see under 'Processes' tab. If you want to see more detailed report (like which processer's using how many CPU cycles and how much RAM, etc.), go to 'View' -> 'Select Columns'. There you can select the information you want to see.

 

[LOUISSSSS]

i understand that other things are taking up my CPU cycles, but is that why P95 is programmed to cut that individual test short to "keep up" with the other worker threads?

 

[lopri]

It's your OS, not the P95. Your OS is assigning CPU cycles to other process than Prime95 in order to keep itself afloat.

 

[LOUISSSSS]

but then why does p95 automatically skip to its next set of tests after that?

 

[myocardia]

It doesn't. Prime95 has a timer for how long it runs each thread. At the end of that time, it starts the next.