Is it possible to disable benchmarking while torture tests are running?

ZFR · 2018-02-02, 12:42

Hi,
I've replaced my motherboard and updated my Prime95 to run torture tests on it before continuing with GIMPS.
I'd lilke to run a test for 24+ hours, however when I leave it for the night, it stops around 5:30 to do benchmarking. Like so:

Code:

[Main thread Feb 2 05:52] Benchmarking multiple workers to tune FFT selection.
[Main thread Feb 2 05:52] Execution halted.
[Main thread Feb 2 05:53] Timing 4480K FFT, 4 cores, 4 workers.  Average times: 36.85, 35.82, 36.03, 35.77 ms.  Total throughput: 110.75 iter/sec.
...

Is ther any way to stop this from happening while torture tests are running? Thanks.

heliosh · 2018-02-02, 14:30

Quote:

Originally Posted by undoc.txt

The program automatically runs benchmarks to aid in optimal FFT selection. It looks at worktodo.txt for upcoming exponents to test and the amount of benchmarking already done to decide if more benchmarks are needed. You can disable this feature by adding to prime.txt:
AutoBench=0

.

ZFR · 2018-02-02, 14:40

Thank you.

Dubslow · 2018-02-02, 19:04

I would argue that it should automatically be off for torture testing, without requiring the user to manually disable it (and then re-enable it for regular work again).

Prime95 · 2018-02-02, 20:18

Quote:

Originally Posted by Dubslow

I would argue that it should automatically be off for torture testing, without requiring the user to manually disable it (and then re-enable it for regular work again).

I agree.

2018-02-02, 12:42	#1
ZFR Feb 2008 Meath, Ireland 5·37 Posts	Is it possible to disable benchmarking while torture tests are running? Hi, I've replaced my motherboard and updated my Prime95 to run torture tests on it before continuing with GIMPS. I'd lilke to run a test for 24+ hours, however when I leave it for the night, it stops around 5:30 to do benchmarking. Like so: Code: [Main thread Feb 2 05:52] Benchmarking multiple workers to tune FFT selection. [Main thread Feb 2 05:52] Execution halted. [Main thread Feb 2 05:53] Timing 4480K FFT, 4 cores, 4 workers. Average times: 36.85, 35.82, 36.03, 35.77 ms. Total throughput: 110.75 iter/sec. ... Is ther any way to stop this from happening while torture tests are running? Thanks. Last fiddled with by ZFR on 2018-02-02 at 12:43

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
SIGSEGV in xi3eK8 running torture test	GordonWade	Information & Answers	10	2018-02-18 00:07
Torture and Benchmarking test of Prome95.Doubts in implementation	paramveer	Information & Answers	32	2012-01-15 06:05
Can I just start Prime95 by running torture test?	marks9GIMPS	Information & Answers	5	2011-06-05 18:44
LL tests running at different speeds	GARYP166	Information & Answers	11	2009-07-13 19:39
How to use Prime95 For benchmarking and torture testing only	Cyclamen Persicum	Software	2	2004-04-03 14:52

2018-02-02, 14:40	#3
ZFR Feb 2008 Meath, Ireland 5×37 Posts	Thank you.

2018-02-02, 19:04	#4
Dubslow Basketry That Evening! "Bunslow the Bold" Jun 2011 40<A<43 -89<O<-88 3·29·83 Posts	I would argue that it should automatically be off for torture testing, without requiring the user to manually disable it (and then re-enable it for regular work again).