1 Attachment(s)
The Raspberry Pi B+ doing BOINC
It has been a week or so since I got my first SBC (Single Board Computer, it has Mobo, RAM and CPU all on one SOC, System-On a-Chip) on BOINC.
It went all very smooth: load the Noobs that you can download from the Raspberry website on a SD card of at least 8GB (I use 16GB just to be sure), insert the SD card,
apply power, let the system start up, install BOINC
Code:
# sudo apt-get install boinc
-and off you go.
As I use BAM!, all projects that I have defaulted there were made active on the Raspi, which included projects without applications for the Raspi. So I had to divide my boxen/hosts into groups. It will come as no surprise to e.g. vaughan that BAM! had some nasty surprises here when more than one box/host was in a group, luckily this did not affect the workings of the Raspi as it is the sole member of my group 'ARM11 on Raspbian'.
What is in that group?
- A Raspberry Pi Model B+, running a Linux 3.18.7+ kernel (Debian Wheezy)
- CPU : A Broadcom ARMv6-compatible processor ARM11, rev 7 (v6l), in short ARM1176JZF-S aka BCM2835 (for the full SOC)
- Features : swp, half, thumb, fastmult, VFP, edsp, java/jazelle, tls
I tried these settings:
Speed in MHz |
Floating Point MIPS (Whetstone) per CPU |
Integer MIPS (Dhrystone) per CPU |
700 |
222 |
926 |
800 |
266 |
1073 |
950 |
323 |
1275 |
1000 |
338 |
1355 |
At 1000MHz it is more responsive and, due to its nice red Lego casing, not hot at all. Attachment 344
My Raspi2 is the sole member of my group 'ARM Cortex-A7 on Raspbian'.
What is in the group?
- A Raspberry Pi 2 Model B, running a Linux 3.18.7+ kernel (Debian Jessie)
- CPU : A Broadcom ARMv7A-compatible processor ARM Cortex-A7, rev 5 (v7l), aka BCM2836 (for the full SOC)
- Features : half, thumb, fastmult, VFP, edsp, NEON, VFPv3, tls, VFPv4, idiva, idivt, VFPd32, lpae, evtstrm
For the Raspberry Pi 2 i got these values (before and after armhf update, and later integer update):
Speed in MHz |
Floating Point MIPS (Whetstone) per CPU |
Integer MIPS (Dhrystone) per CPU |
1000 |
293 |
1163 |
1000 |
489 |
1448 |
1000 |
489 |
1944 |
Though the MIPS values originally were less than the single-core Raspberry Pi B+ @1000 MHz, having four -more modern- cores certainly gives an advantage.
Updating the armhf (hardware floating point) and integer files gave a tremendous boost to the benchmarks, now to see what it offers in real life...
It is not just MHz and MIPS what counts when it comes to real-life performance!
Project |
Avg. running time in hours |
Avg. credit |
Green light? |
Orange light? |
Red light? |
Albert@Home |
25 |
100 |
Yes |
- |
- |
Asteroids@Home |
gets stuck at 7% (Raspi B+)
100 (Raspi 2) |
480 |
Yes |
- |
- |
Collatz@Home |
tbd |
tbd |
Yes |
- |
- |
Einstein@Home |
25 |
63 |
Yes |
- |
- |
Enigma@Home |
5 |
30 |
Yes |
- |
- |
FiND@Home |
tbd |
tbd |
Yes |
- |
- |
MilkyWay@Home |
tbd |
tbd |
RasPi 2 |
Raspi B+ |
- |
QCN (Quake Catcher Network) |
tbd |
tbd |
RasPi B+* |
- |
RasPi 2** |
Radioactive@Home |
tbd |
tbd |
RasPi 2* |
- |
- |
Seti@Home |
110 |
- |
RasPi 2 |
RasPi B+ |
- |
theSkyNet POGS |
tbd |
tbd |
- |
- |
RasPi 2** |
WUProp |
3.5 (Raspi B+)
7 (Raspi 2) |
7 (Raspi B+)
14 (Raspi 2) |
RasPi 2 |
RasPi B+ |
- |
Yoyo@Home |
tbd |
28.86 (Raspi B+)
80 (Raspi 2) |
Yes |
- |
- |
] Legenda |
tbd=To be determined
*=Needs a sensor though
**=Will only run using Android as OS |
- =
no data/not applicable |
Green light=
Works out-of-the-box |
Orange light=
Needs some fiddling |
Red light=
Refuses to work |
It appears that most 'native' applications have a problem of sorts -or that connecting through BAM! may seem pretty smart, but you'd better do it the 'hard' way,
as Daniel Carrion explains here at Burdeview. Worked for MilkyWay and WUProp, but at first not for Seti@Home. Seti started after a second round of fiddling though.
Most of the out-of-the-box projects can be brought into action by suspending all others, FiND appears to have run out of work for the Raspberry, OProject has been retired according to BOINCStats -they retired a lot of projects recently- and POGS has trouble with downloading an *.png image.
Looking at the table above though it suddenly dawned upon me that the problems are pretty much all with projects that I normally run as GPU-only.
Now the Raspberry has a pretty potent GPU -some 24 GFLOP as compared to other SBCs that mostly have to do with around 1 or 2 GFLOP-, but nobody has yet written a GPU BOINC application for the Raspberry.
So I may just need different profiles for the Raspberry (location in the project page like 'Home' or 'Work' or 'School' instead of 'default') that allow for CPU crunching of these projects!
Soon to be updated yet again...