Next-gen Odroid announcement - Page 7

paulunderwood · 2019-06-18, 19:49

Code:

[Jun 18 15:01:01] M914***** Iter# = 7950000 [ 8.70% complete] clocks = 00:17:53.663 [107.3663 msec/iter] Res64: 4D01D71A8D0A3597. AvgMaxErr = 0.079252374. MaxErr = 0.109375000. Residue shift count = 26123447.
[Jun 18 15:18:54] M914***** Iter# = 7960000 [ 8.71% complete] clocks = 00:17:51.167 [107.1167 msec/iter] Res64: 1C64720358E8B548. AvgMaxErr = 0.079291315. MaxErr = 0.117187500. Residue shift count = 27945342.
[Jun 18 15:37:26] M914***** Iter# = 7970000 [ 8.72% complete] clocks = 00:18:29.727 [110.9727 msec/iter] Res64: 4E201EDBE693F80B. AvgMaxErr = 0.079358624. MaxErr = 0.109375000. Residue shift count = 11087326.
[Jun 18 15:55:43] M914***** Iter# = 7980000 [ 8.73% complete] clocks = 00:18:11.301 [109.1301 msec/iter] Res64: 46A3EF697E0B7999. AvgMaxErr = 0.079285226. MaxErr = 0.109375000. Residue shift count = 35877845.
[Jun 18 16:13:34] M914***** Iter# = 7990000 [ 8.74% complete] clocks = 00:17:42.310 [106.2310 msec/iter] Res64: CA50AFF28616551E. AvgMaxErr = 0.079323541. MaxErr = 0.109375000. Residue shift count = 54051585.
[Jun 18 16:31:38] M914***** Iter# = 8000000 [ 8.75% complete] clocks = 00:17:58.692 [107.8693 msec/iter] Res64: E86895B693971CA9. AvgMaxErr = 0.079318311. MaxErr = 0.109375000. Residue shift count = 39944003.
[Jun 18 16:49:33] M914***** Iter# = 8010000 [ 8.76% complete] clocks = 00:17:50.335 [107.0336 msec/iter] Res64: 638A7E1A7236BE15. AvgMaxErr = 0.079304779. MaxErr = 0.109375000. Residue shift count = 61849059.
[Jun 18 17:07:03] M914***** Iter# = 8020000 [ 8.77% complete] clocks = 00:17:26.925 [104.6925 msec/iter] Res64: 35938AA44D32EB85. AvgMaxErr = 0.079322753. MaxErr = 0.109375000. Residue shift count = 4298838.
[Jun 18 17:24:56] M914***** Iter# = 8030000 [ 8.78% complete] clocks = 00:17:48.605 [106.8605 msec/iter] Res64: EC952DCA2CBF36C9. AvgMaxErr = 0.079391460. MaxErr = 0.125000000. Residue shift count = 13515903.
[Jun 18 17:42:58] M914***** Iter# = 8040000 [ 8.80% complete] clocks = 00:17:59.617 [107.9617 msec/iter] Res64: 841E0FE38CC87672. AvgMaxErr = 0.079387793. MaxErr = 0.109375000. Residue shift count = 8677722.
[Jun 18 18:01:06] M914***** Iter# = 8050000 [ 8.81% complete] clocks = 00:18:05.056 [108.5057 msec/iter] Res64: DEC2F07E46B82700. AvgMaxErr = 0.079358276. MaxErr = 0.109375000. Residue shift count = 13727072.
[Jun 18 18:18:55] M914***** Iter# = 8060000 [ 8.82% complete] clocks = 00:17:46.838 [106.6838 msec/iter] Res64: 7F1DD640CD6E9735. AvgMaxErr = 0.079310718. MaxErr = 0.109375000. Residue shift count = 29121784.
[Jun 18 18:36:39] M914***** Iter# = 8070000 [ 8.83% complete] clocks = 00:17:41.997 [106.1997 msec/iter] Res64: 3E50C0CB0075B71D. AvgMaxErr = 0.079339769. MaxErr = 0.109375000. Residue shift count = 86075204.
[Jun 18 18:54:28] M914***** Iter# = 8080000 [ 8.84% complete] clocks = 00:17:46.468 [106.6469 msec/iter] Res64: 6CD28733082AA7C5. AvgMaxErr = 0.079340430. MaxErr = 0.109375000. Residue shift count = 43325490.
[Jun 18 19:15:57] M914***** Iter# = 8090000 [ 8.85% complete] clocks = 00:21:26.050 [128.6051 msec/iter] Res64: 0AC48D068E32D8F1. AvgMaxErr = 0.079287323. MaxErr = 0.125000000. Residue shift count = 32575426.
[Jun 18 19:42:27] M914***** Iter# = 8100000 [ 8.86% complete] clocks = 00:26:28.569 [158.8570 msec/iter] Res64: 71329024D00CDCCC. AvgMaxErr = 0.079361060. MaxErr = 0.109375000. Residue shift count = 67915085.
[Jun 18 20:09:00] M914***** Iter# = 8110000 [ 8.87% complete] clocks = 00:26:30.682 [159.0682 msec/iter] Res64: D74F2FF344960F67. AvgMaxErr = 0.079284901. MaxErr = 0.109375000. Residue shift count = 61052515.
[Jun 18 20:35:27] M914***** Iter# = 8120000 [ 8.88% complete] clocks = 00:26:24.374 [158.4374 msec/iter] Res64: C11BB80026F99829. AvgMaxErr = 0.079352954. MaxErr = 0.109375000. Residue shift count = 30064815.

I guess the a73 was being used a little whilst I was just askyping.

paulunderwood · 2019-06-18, 20:07

Quote:

Originally Posted by ewmayer

Thanks - those strike me as unremarkable ... the maxROEs are generally quite granular and have fractions of form p/q, with q a small power of 2, as attractors - in your case the dominant maxROE value is 0.109375 = 7/64, with occasional excursions up to 0.125 = 1/8. The variable-length DWT-weights-chain code in v19 which gave you the ~3% speedup also appears more prone to these kinds of blips.

I suggest when next you happen to have a decently long interval without Firefox open-tab-crashage, check the overlapping stat-file entries and see if any 0.125 maxROEs occurred. If there really were a data corruption issue at work here, one would expect it to lead to random anomalous ROEs, not ones which are precisely in a consistent range.

Okay.

I checked the logs in /var/log and there was nothing reported that indicated a hardware issue.

(I too have pressed "edit" rather than "quote" as a mod

)

ewmayer · 2019-06-18, 20:26

Bit of an hit-edit-instead-of-reply-glitch on my part there ... I accidentally overwrote Paul's ROE-snippet post with my reply. He restored the former, but what you see in his followup is his reply to my now-gone reply-in-place-of-his-original-post. Clear as mud!

paulunderwood · 2019-06-18, 21:44

I had another browser tab crash with a change in Max ROE. I upgraded the system which upgraded dbus amongst other things -- maybe it will be more stable now.

ewmayer · 2019-06-18, 23:20

If the browser crashes really are impacting the Mlucas run in the manner you describe, that is bizarre - might be a good idea to get someone to do an early DC of that exponent, or use Prime95/mprime on some x86 hardware of your own to do the secondary run yourself, with interimResidues (or whatever that Prime95 option is called) enabled.

This sort of thing is why I started all my cellphone nodes on DCs before switching them to first-time LL.

paulunderwood · 2019-06-19, 00:40

Quote:

Originally Posted by ewmayer

If the browser crashes really are impacting the Mlucas run in the manner you describe, that is bizarre - might be a good idea to get someone to do an early DC of that exponent, or use Prime95/mprime on some x86 hardware of your own to do the secondary run yourself, with interimResidues (or whatever that Prime95 option is called) enabled.

This sort of thing is why I started all my cellphone nodes on DCs before switching them to first-time LL.

I downloaded, built and configured Mlucas_v18. It will take less than a day and half to see I have all matching RES64.

Code:

    Mlucas 18.0

    http://www.mersenneforum.org/mayer/README.html

INFO: testing qfloat routines...
CPU Family = x86_64, OS = Linux, 64-bit Version, compiled with Gnu C [or other compatible], Version 9.1.0.
INFO: Build uses AVX2 instruction set.
INFO: Using inline-macro form of MUL_LOHI64.
INFO: MLUCAS_PATH is set to ""
INFO: using 64-bit-significand form of floating-double rounding constant for scalar-mode DNINT emulation.
Setting DAT_BITS = 10, PAD_BITS = 2
INFO: testing IMUL routines...
INFO: System has 4 available processor cores.
INFO: testing FFT radix tables...
Set affinity for the following 4 cores: 0.1.2.3.
NTHREADS = 4
 looking for worktodo.ini file...
 worktodo.ini file found...checking next exponent in range...
INFO: primary restart file p914***** not found...looking for secondary...
INFO: no restart file found...starting run from scratch.
mers_mod_square: Init threadpool of 4 threads
radix16_dif_dit_pass pfetch_dist = 4096
radix16_wrapper_square: pfetch_dist = 4096
Using 4 threads in carry step

Code:

M9141*****: using FFT length 5120K = 5242880 8-byte floats, initial residue shift count = 6324947
 this gives an average   17.435125541687011 bits per digit
Using complex FFT radices       160        16        32        32
[Jun 19 01:18:48] M914***** Iter# = 10000 [ 0.01% complete] clocks = 00:02:25.632 [ 14.5632 msec/iter] Res64: 771472D5BD75657A. AvgMaxErr = 0.061904874. MaxErr = 0.078125000. Residue shift count = 24468007.

ewmayer · 2019-06-19, 06:02

Paul, is that avx2 system hyperthreaded? If so, you may get a modest boost from using -cpu 0:7.

paulunderwood · 2019-06-19, 06:25

Quote:

Originally Posted by ewmayer

Paul, is that avx2 system hyperthreaded? If so, you may get a modest boost from using -cpu 0:7.

It is, but I have it switched off in BIOS. I can't be bothered with monitor changes and reboots etc.

I have matching RES64 1.66% / 10% -- when the AVX2 machine catches up with the N2 and everything seems okay. I will kill v18 and let the box go on with its other task: LLR

Incidentally, no more browser tab crashes have occurred -- which might be due to the OS upgrade.

paulunderwood · 2019-06-20, 14:03

I have matching RES64 at 10%. So I will let the N2 carry on with completing the LL test -- I have stopped the AVX2 run. (Again: no browser tab crashes after the OS upgrade.)

ewmayer · 2019-06-20, 19:12

That's good news - I'll be interested to hear if you get any more ROE = 0.125 occurrences with the browser-crash issue fixed.

paulunderwood · 2019-06-20, 19:34

Quote:

Originally Posted by ewmayer

That's good news - I'll be interested to hear if you get any more ROE = 0.125 occurrences with the browser-crash issue fixed.

Yes, it is giving some of those ROE.

A new problem: the iteration times have jumped to 109.3 when idle, up from 102.5. The only difference is I am running from a @reboot command in crontab. I will renice it 0 and see if that makes an improvement

I just touched the heatsink -- it is hot. I will have to think of a way to cool it. Maybe there is a USB fan I can put under it.

2019-06-18, 21:44	#70
paulunderwood Sep 2002 Database er0rr 5×937 Posts	I had another browser tab crash with a change in Max ROE. I upgraded the system which upgraded dbus amongst other things -- maybe it will be more stable now. Last fiddled with by paulunderwood on 2019-06-18 at 22:06

2019-06-20, 14:03	#75
paulunderwood Sep 2002 Database er0rr 1001001001101₂ Posts	I have matching RES64 at 10%. So I will let the N2 carry on with completing the LL test -- I have stopped the AVX2 run. (Again: no browser tab crashes after the OS upgrade.) Last fiddled with by paulunderwood on 2019-06-20 at 14:03

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
mprime on Odroid 64bit	ET_	Software	2	2017-02-24 15:42
GPU72 plans post-announcement	garo	GPU to 72	25	2013-03-04 10:11
The Prime Announcement Thread	axn	Sierpinski/Riesel Base 5	61	2008-12-08 16:28
Subscribing to announcement thread	fetofs	GMP-ECM	1	2006-05-30 04:32
Fourth known factor of M(M31) (preliminary announcement)	ewmayer	Operazione Doppi Mersennes	22	2005-07-06 00:33

2019-06-18, 20:26	#69
ewmayer ∂²ω=0 Sep 2002 República de California 2²×2,939 Posts	Bit of an hit-edit-instead-of-reply-glitch on my part there ... I accidentally overwrote Paul's ROE-snippet post with my reply. He restored the former, but what you see in his followup is his reply to my now-gone reply-in-place-of-his-original-post. Clear as mud!

2019-06-18, 23:20	#71
ewmayer ∂²ω=0 Sep 2002 República de California 2²·2,939 Posts	If the browser crashes really are impacting the Mlucas run in the manner you describe, that is bizarre - might be a good idea to get someone to do an early DC of that exponent, or use Prime95/mprime on some x86 hardware of your own to do the secondary run yourself, with interimResidues (or whatever that Prime95 option is called) enabled. This sort of thing is why I started all my cellphone nodes on DCs before switching them to first-time LL.

2019-06-19, 06:02	#73
ewmayer ∂²ω=0 Sep 2002 República de California 2²×2,939 Posts	Paul, is that avx2 system hyperthreaded? If so, you may get a modest boost from using -cpu 0:7.

2019-06-20, 19:12	#76
ewmayer ∂²ω=0 Sep 2002 República de California 2²·2,939 Posts	That's good news - I'll be interested to hear if you get any more ROE = 0.125 occurrences with the browser-crash issue fixed.