One thing that I find interesting:

The tasks that I run on my desktop differ a lot in computation time, from 1.5h to more than 3 hours. The tasks on my Rpi have been very stable in runtime for the last few days, each one was around 10 hours.

Hi,
Running time of the tasks may vary. It is normal for them to differ by a lot. Don't expect running time to be the same for every task for the given platform.

Cheers!
Georgi

---

“The good thing about science is that it's true whether or not you believe in it.” ― Neil deGrasse Tyson

This is exactly what I meant, I remember you saying that the task time varies, and I saw it on the x86 desktop, what surprised me was that on the RPi the task time did not vary :)

What happened on your host was by pure chance.
Take a look mine: https://asteroidsathome.net/boinc/results.php?hostid=729912
CPU time form 2 hours 12 min 59 sec to 15 hours 32 min 44 sec with average around 10 hours.

---

“The good thing about science is that it's true whether or not you believe in it.” ― Neil deGrasse Tyson

Haha, thanks, guess I'm just lucky :)

Hi,

i just noticed that the 102.14 aarch64 version supports Glibc 2.28 systems.

I am now getting valid results on Asus Tinker Board 2 (OP1 - RK3399 with Armbian) and Asus Tinker Edge R (RK3399 Pro with Debian Buster). Nice job!

I wish you all the best for the new year 2023! :-)

Spectrum

---

Yes, we've done some changes in builds. Hope for the best.

If any issues come up, please send your feedback.

Happy holydays!

---

“The good thing about science is that it's true whether or not you believe in it.” ― Neil deGrasse Tyson

Cool stuff, just tested aarch64 version on following hardware, all with stock cooling/no cooling, works perfectly fine:

Oracle Cloud Ampere Altra (ubuntu) ~2.2hrs/task
Samsung A50 smartphone (proot-distro@termux) ~18hrs/task
Tannix T3 Amlogic S905x3 TV box (armbian) ~29hrs/task
Huawei P8 Max smartphone (ubuntu@userland) ~37hrs/task
X88Pro Rockchip rk3318 TV box (armbian) ~68hrs/task

Hi,

just a quick greetings / thanks from France for this arm64 bits release

Just noticed it yesterday. I just set Asteroids@Home running on a bunch of cooled (but not very loaded) arm64 Bullseye running RasPies (used as 24/24 running low consumption servers/test devices).

Memory usage is very low, making it suitable for low memory devices

Universe@Home wasn't loading any work on the arm64 architecture despite of the compatibility shown on the BOINC project list. And Einstein@Home is using a lot of RAM memory (~200 MiB per task), which is too much to run on 4 cores when using 1GB RAM devices without having catastrophic crashes all the times (Linux kernels having become completely unable to keep running fine when something uses too much RAM... for a bunch of years already. Seems it's never going to be repaired)

Anyway, in short, nice work!

This past Spring, i upgraded my pi 3s to 64 bit Raspian (Buster). I had not seen this announcement and was looking for apps to try. I bumped into Asteroids early, probably because it's early in the alphabet. These 3 pi 3s mainly pushed my Asteroids to 100k hours (WUProp helps me see which machines are still running). Last month i picked up a Libre AML-S905X-CC, which looks much like a pi 3 and runs a modified version of the same Buster OS. It ran Asteroids find. Averaging about 40 apps run on each of these shows the Libre to be about the same speed, at least for Asteroids. The Libre has 2 GB RAM, which is why i bought one. It wasn't for Asteroids. The pi 4 is about 4x faster than the pi 3 for Asteroids. I have a 2009 vintage AMD Phenom 2 956 which is about 15x faster than the pi 3. All these machines have cooling.

To use a aarch64 Pi on Universe you need to add the 32 bit libraries, i.e. , armhf, because all the Universe apps are 32bit for the cpu apps.

Do this:

sudo dpkg --add-architecture armhf

sudo apt update

sudo apt install libstdc++6:armhf libgomp1:armhf libboinc7:armhf

sudo reboot

---

A proud member of the OFA (Old Farts Association)

Hello :)

I did a test to see how much faster the new Pi 5 is in comparison to the 4b model and I thought it would be interesting for you. In short, the new Pi 5 is three times faster in crunching Asteroids@Home than the previous model.

Things to mention:
- In Einstein@Home the gains in speed were only ~30%, a significant difference in comparison to A@H
- Asteroids have been pushing the CPU thermally much more than E@H
- When crunching, for the Pi4, the task name was "Period Search Application v102.14aarch64-unknown-linux-gnu", while for the 5 it was "Period Search Application v102.14aarch64". Would that make a difference? And what is even weirder, I just checked, when I open the computer list and browse the tasks per computer, both Pis are now showing the task name to be "Period Search Application v102.14aarch64-unknown-linux-gnu". Is it possible that it changed recently?

Here is the link to the blog post, inside you can find the detailed benchmark results, and you can also download the raw test data if you want to do your own analysis.

https://stfn.pl/blog/18-rpi4-rpi5-asteroids/

Great job stfn!

---

“The good thing about science is that it's true whether or not you believe in it.” ― Neil deGrasse Tyson

To use a aarch64 Pi on Universe you need to add the 32 bit libraries, i.e. , armhf, because all the Universe apps are 32bit for the cpu apps.

Do this:

sudo dpkg --add-architecture armhf

sudo apt update

sudo apt install libstdc++6:armhf libgomp1:armhf libboinc7:armhf

sudo reboot

and alter your cc_config.xml to contain these two lines (WCG needs the v7l version)
<cc_config>
<options>
<alt_platform>arm-unknown-linux-gnueabihf</alt_platform>
<alt_platform>armv7l-unknown-linux-gnueabihf</alt_platform>
</options>
</cc_config>

---

Hi!

I am doing a new round of testing of the Pi 5, now with added spice :) And I wanted to ask: Can I assume that the size of the current typical workunit (in terms of computation) is similar to a workunit a year ago?

---

my blog about raspberry pis and astrophotography

in terms of computation, they're similar. However the arm app has been optimized, so Pi 4/5 should be more efficient and finish faster.

if you want to run some perf tests, I recommend doing so in a standalone mode. This way you can always test the same work unit and reliably compare results across multiple devices.

download the app
https://asteroidsathome.net/boinc/download/period_search_10221_aarch64-unknown-linux-gnu__aarch64_armv8-a_asimd
and place a sample WU period_search_in in the same folder
https://github.com/AsteroidsAtHome/PeriodSearch/blob/dev/period_search_opencl_amd/input_period_search/period_search_in

I was suspicious about your runtimes and it turns out that for some reason, the latest linux arm app doesn't contain the latest optimizations, I let Georgi know. Feel free to use the older version which should be faster.
https://asteroidsathome.net/boinc/download/period_search_10220_aarch64-unknown-linux-gnu

That explains a lot :) The full story is that I bought an NVMe HAT for my Pi 5 and I am testing if it makes crunching BOINC faster. So far I have seen speed gains of around 30% when computing Einstein@Home, and for Asteroids@Home, the difference was around 3%, so basically nothing.

I will crunch another batch of tasks, but please let me know how can I force to crunch a particular app? Where to put the downloaded file? I've never done this before.

---

my blog about raspberry pis and astrophotography

You'll have to run a anonymous platform with an app_info file to make use specifically of the older 10220 application.

I have edited what I use to just the cpu app for you.

<app_info>

<app>
<name>period_search</name>
<user_friendly_name>Period Search Application</user_friendly_name>
<non_cpu_intensive>0</non_cpu_intensive>
</app>


<file>
<name>period_search_10220_aarch64-unknown-linux-gnu</name>
<executable/>
</file>


<app_version>
<app_name>period_search</app_name>
<version_num>10220</version_num>
<platform>aarch64-unknown-linux-gnu</platform>
<avg_ncpus>1.000000</avg_ncpus>
<api_version>7.17.0</api_version>
<file_ref>
<file_name>period_search_10220_aarch64-unknown-linux-gnu</file_name>
<main_program/>
</file_ref>
</app_version>

</app_info>


You'll have to download the file from the link provided and place it in the Asteroids project folder.

---

A proud member of the OFA (Old Farts Association)

Just noticed that that I had received this new 10221 aarch64 app on my Jetson Nano. Unfortunately it has errored out all the work sent to it.

Looks like the app expects glibc version 2.29.

<core_client_version>7.9.3</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)</message>
<stderr_txt>
../../projects/asteroidsathome.net_boinc/period_search_10221_aarch64-unknown-linux-gnu__aarch64_armv8-a_asimd: /lib/aarch64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by ../../projects/asteroidsathome.net_boinc/period_search_10221_aarch64-unknown-linux-gnu__aarch64_armv8-a_asimd)

</stderr_txt>

I'm going to have to deploy an app_info on this host also I see and revert to the 10220 version app.

---

A proud member of the OFA (Old Farts Association)