High-Speed Linux-BRP-App for Raspberry Pi 3
10 Sep 2016 7:00:12 UTC
Topic 200980
(moderation:
Hello,
as I have promised here are a BRP-App compiled for the RPI3. Due to the limited RAM of the RPI3 I've made two Versions. You could select that one that fits your needs.
Out-of-Place Version:
If you running a 24/7-cruncher with a minimal Linux, this Version is perfect for you. It have the highes RAM-requirements but it is fastest Version.
The runtime is ~20500sec but it need ~201MB of RAM per Task.
In-Place Version:
* Attention! This Version makes Problems on some Devices! Only try it when you know how to switch back! And keep a Eye on it *
If you using your RPI3 not only for crunching and doing other thinks in parallel (or you running a Linux with a GUI), you should take this Version. It is al little bit slower than the Out-of-Place Version but needs much less RAM.
The runtime is ~24000sec but it needs only ~123MB of RAM per Task.
Installation:
The downloaded Archive contains all folders(projects/einstein.phys.uwm.edu). You can simply extract it in your boinc-client-folder.
Attention: All started & downloaded Workuntits will be abort !!!
- go to your boinc-client folder: cd /var/lib/boinc-client
- log in as root: su
- download the Archive:
- out-of-place Version: wget http://kerbodyne.com/einstein/einstein_32bit_0.13-OP.tar
- in-place Version: wget http://kerbodyne.com/einstein/einstein_32bit_0.13-IP.tar
- stop your boinc-client: systemctl stop boinc-client
- extract the archive (maybe you have to kill running BRP-Apps):
- out-of-place Version: tar -xvf einstein_32bit_0.13-OP.tar
- in-place Version: tar -xvf einstein_32bit_0.13-IP.tar
- Start your boinc client: systemctl start boinc-client
Special Thanks to Koschi for Hosting this.
Notes:
This Version is not only restricted to the Raspberry PI 3 it may run on other Devices with a Cortex-A53, but it is highly optimized for the Raspberry Pi 3.
If running a other Cortex-A53-device that has 64bit(AARCH64)-support you should consider using this Version for best performace.
I have committed one Pi3 to
)
I have committed one Pi3 to the new application. Waiting to see the results and the avg temps over an 8 hour period before committing other Pi3s. I am running full desktop on all my Pi3s. And I am running the "out-of-place-version" even though you don't recommend it. The "out-of-place" version is running 4 concurrent tasks as are my other Pi3s with the project delivered application.
Early on temps for the new app on a Pi3 are around 5C higher then the other Pi3s using the E@H app. All Pis are in tunnels with heat sinks and cooling fans.
I will let you know within a few hours the initial results.
I only don't recomend the use
)
I only don't recomend the use of the out-of-place on a System with a GUI because you probably want to do somethink with your desktop-system. Like using Firefox or somethink else... And you maybe running out of RAM and start to use swap. The use of swap isn't a good idea on a SD-Card.
If you have enough free RAM. Your fine with the out-of-place + GUI-system.
With a "little bit" of overclocking I've now down to ~18ksec running 4 concurrent tasks on my RPI3.
Not sure what happened but I
)
Not sure what happened but I was getting errors using the "out-of-place-version" - jobs not completing. I cleaned up the Pi and started over using the "in-place-version". It will be another ~5 hours or so before I can report anything.
One Pi3 updated (took a while
)
One Pi3 updated (took a while to flush its cache). According to BOINCtasks it's using 201Mb per task Using out of place.
Looking through my recent results they have been taking 63k seconds a task since about the 3rd of September. I am not sure if it's some update or something else that has caused it or maybe the tasks need more computation than before.
MarksRpiCluster
robl wrote:Not sure what
)
Can you give me a link to that device (or one of the Tasks that gave you a error), I want to look into the Stderr, maybe it was only some kind of permission-problem.
Strange think. I really don't know what causes that high run-times. On my Odroids the runtime is constant for over one month.
N30dG wrote:PorkyPies
)
All of mine seem to be consistently doing it so that rules out a particular Pi. Looking through some older (42k second) tasks they appear to be the same angle and such. I think it might be time to wipe this particular Pi and reinstall it with Jessie-Lite and see how it goes.
MarksRpiCluster
N30dG wrote:robl wrote:Not
)
here is the requested link: https://einsteinathome.org/host/12233675/tasks/error
I looked at 2 of the WUs and it appears to be a memory issue. As stated I reverted to the "in-place-version" and those WUs processed as expected. They completed in ~24k seconds vs 41k seconds. Looks like you have done it again. Congrats.
[EDIT] I am running my Pi3s with Ubuntu Mate.
[EDIT] I will run for a couple of more days on this Pi3 and if all checks out install the app on the other Pi3s.
Thank you N30DG! I installed
)
Thank you N30DG!
I installed the in-place version yesterday and it's working great, all tasks validating!
On my RPi3 tasks are now completing just shy of 21000 seconds per task, that's 15000 seconds faster than the NEON_beta app it was running.
I'm running on 3 out of the 4 cores to both reduce heat and be able to use my Pi for other things.
Once again a big thank you and great work!
Wiped the Pi3 I was using and
)
Wiped the Pi3 I was using and reinstalled Jessie-Lite, BOINC and the optimised app. Its now off and running. Interestingly Jessie-Lite seems to have more free memory than Stretch.
Spoke to soon. Seems to have crashed the Pi a few times now. Will try the in-place and see if that helps. Can't see any error messages in the BOINC logs
[edit]
A bit later and the in-place app installed and its crashed again.
MarksRpiCluster
PorkyPies wrote:Wiped the Pi3
)
The following is based upon Ubuntu Mate. It should apply to any Linux OS.
cd /var/lib/boinc-client/projects/einstein.phys.uwm.edu
what effect does the following have from the command line? note the ./
./einsteinbinary_BRP4_0.13IP_AARCH32-unknown-linux-gnu <---this is for the "in-place" version.
The above should give: "Application startup - thank you for supporting Einstein@Home!"
Is the app_info.xml the correct one?, i.e., was the old version overwritten with the new version for this new application. Look inside the xml file it should reference this file: einsteinbinary_BRP4_0.13IP_AARCH32-unknown-linux-gnu if you are using the "in-place" version.
I aborted all running jobs prior to stopping the boinc-client. I then removed the old xml and app file prior to untarring and copying the new application. I then restarted boinc-client. I tried the out of place version and it failed with memory issues being reported in the failed WUs so I fell back to the IP version which is working fine.
Don't know if the above will help but ...