I did run pichart on Pi5 without overclocking and 64bit Bookworm.
57.8 is not much less than the 58.3 reported for "Pi5 Quad A76", which was achieved with 32bit OS I believe.
https://fractal.math.unr.edu/~ejolson/p ... irates.svg
Next I did run pichart after booting into 3000MHz:
I had one lucky run that succeeded, all other runs did fail in "lorenz 96"-
I learned from @trejan that "Increasing the voltage will fix it so it isn't a problem with Pi Chart."
I added over_voltage=3 and rebooted — same problem.
I changed to over_voltage=6 and rebooted -- success.
@ejohlson please add new entry "Pi5 Quad A76 3000MHz — 66.9" for the two consecutive runs below:
The over_voltage settings helped pichart-openmp to complete, but did set overclock bit as well:
https://www.raspberrypi.com/documentati ... ng-options
I did factor RSA-100 with this setup, but over_voltage=6 did reduce previous 3000MHz factoring time of 0:13:30h by 4 seconds only. So I already removed the over_voltage line and rebooted, because neither compiling cado-nfs nor factoring RSA-120 in 5:05:17h had problems with just 3000MHz without over_voltage line in config.txt.
57.8 is not much less than the 58.3 reported for "Pi5 Quad A76", which was achieved with 32bit OS I believe.
https://fractal.math.unr.edu/~ejolson/p ... irates.svg
Next I did run pichart after booting into 3000MHz:
Code:
pi@raspberrypi5:~ $ tail -2 /boot/config.txt arm_freq=3000force_turbo=1pi@raspberrypi5:~ $ I had one lucky run that succeeded, all other runs did fail in "lorenz 96"-
I learned from @trejan that "Increasing the voltage will fix it so it isn't a problem with Pi Chart."
I added over_voltage=3 and rebooted — same problem.
I changed to over_voltage=6 and rebooted -- success.
@ejohlson please add new entry "Pi5 Quad A76 3000MHz — 66.9" for the two consecutive runs below:
pi@raspberrypi5:~ $ sudo cat /sys/devices/system/cpu/cpufreq/policy0/cpuinfo_*_freq
3000000
3000000
3000000
pi@raspberrypi5:~/pichart-39 $ ./pichart-openmp
pichart -- Raspberry Pi Performance OPENMP version 39
Prime Sieve P=14630843 Workers=4 Sec=0.267299 Mops=3495.44
Merge Sort N=16777216 Workers=8 Sec=0.517795 Mops=777.63
Fourier Transform N=4194304 Workers=4 Sec=1.22957 Mflops=375.233
Lorenz 96 N=32768 K=16384 Workers=4 Sec=0.103297 Mflops=31184
My Computer has Raspberry Pi ratio=66.6836
Making pie charts...done.
pi@raspberrypi5:~/pichart-39 $ ./pichart-openmp
pichart -- Raspberry Pi Performance OPENMP version 39
Prime Sieve P=14630843 Workers=4 Sec=0.267184 Mops=3496.95
Merge Sort N=16777216 Workers=8 Sec=0.501396 Mops=803.065
Fourier Transform N=4194304 Workers=8 Sec=1.27101 Mflops=362.998
Lorenz 96 N=32768 K=16384 Workers=4 Sec=0.103847 Mflops=31018.9
My Computer has Raspberry Pi ratio=66.5863
Making pie charts...done.
pi@raspberrypi5:~/pichart-39 $
The over_voltage settings helped pichart-openmp to complete, but did set overclock bit as well:
https://www.raspberrypi.com/documentati ... ng-options
Setting any overclocking parameters to values other than those used by raspi-config may set a permanent bit within the SoC, making it possible to detect that your Raspberry Pi has been overclocked. The specific circumstances where the overclock bit is set are if force_turbo is set to 1 and any of the over_voltage_* options are set to a value > 0. See the blog post on Turbo Mode for more information.
I did factor RSA-100 with this setup, but over_voltage=6 did reduce previous 3000MHz factoring time of 0:13:30h by 4 seconds only. So I already removed the over_voltage line and rebooted, because neither compiling cado-nfs nor factoring RSA-120 in 5:05:17h had problems with just 3000MHz without over_voltage line in config.txt.
Statistics: Posted by HermannSW — Tue Dec 12, 2023 9:39 pm