| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Active Research
Forum: OpenPandemics - COVID-19 Project
Thread: support for 64 bit ARM processors. |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 9
|
|
| Author |
|
|
mwroggenbuck
Advanced Cruncher USA Joined: Nov 1, 2006 Post Count: 85 Status: Offline Project Badges: 
|
Does OpenPandemics support 64 bit ARM processors? Specifically, I am using Raspberry Pi 400. The hardware is 64 bits, but the standard Raspberry Pi OS is only 32 bits, so only 32 bit executables are run. However, there is a beta of Raspberry Pi OS that is 64 bits. If there is a 64-bit OpenPandemics (ARM) executable, I show get more throughput by going to 64 bits. However, it does not make any sense to try if no 64 bit executable is available.
I looked around the forums for this, and found a few conversations, but nothing that seemed to be definitive (most conversations were about running 32 bit executables on 64 bit OS/hardware). I would appreciate a solid answer on this. Is there a 64 bit ARM executable? Maybe the project owners can answer it? |
|||
|
||||
|
Umlauf
Advanced Cruncher Joined: Mar 20, 2020 Post Count: 52 Status: Offline Project Badges: 
|
Hello,
----------------------------------------yes OPN supports 64bit ARM processors. You need to define alternate_platforms in the cc_config. Take a look here: https://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,42687 I ´m running OPN on 3 ARM-machines (odroid). [Edit 1 times, last edit by Umlauf at Feb 17, 2021 4:28:00 PM] |
||
|
|
mwroggenbuck
Advanced Cruncher USA Joined: Nov 1, 2006 Post Count: 85 Status: Offline Project Badges:
|
I assume you are doing this under Linux. If you run the file command on the actual OpenPandemic executable, does it show 64 bits? I just want to be sure. Reading the link you gave, it sounded like running 32 bit application on a 64 bit OS/hardware. That might give a little throughput increase, but not as much as using native 64 bit instructions in the actual executable. The file <executable> command should give this information.
----------------------------------------I do appreciate the information. [Edit 3 times, last edit by mwroggenbuck at Feb 17, 2021 4:51:03 PM] |
||
|
|
Umlauf
Advanced Cruncher Joined: Mar 20, 2020 Post Count: 52 Status: Offline Project Badges:
|
I am doing this under linux.
No OPN (and when going life MCM(there was only a beta in october 2020 for arm)) only supports 32 bit. This is the reason for the requirement of the alternate platform information. |
||
|
|
mwroggenbuck
Advanced Cruncher USA Joined: Nov 1, 2006 Post Count: 85 Status: Offline Project Badges:
|
Thank you for the information. I suspected there was only a 32 bit executable, but I wanted to ask.
|
||
|
|
spRocket
Senior Cruncher Joined: Mar 25, 2020 Post Count: 280 Status: Offline Project Badges: 
|
Hello, yes OPN supports 64bit ARM processors. You need to define alternate_platforms in the cc_config. Take a look here: https://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,42687 I ´m running OPN on 3 ARM-machines (odroid). An alternative approach on Raspberry Pi is to define arm_64bit=1 in your /boot/config.txt file. That requires no configuration changes to BOINC. I have a couple of Pi 400s, and one each of Pi 4, 3B+, and 3B crunching for me. |
||
|
|
mwroggenbuck
Advanced Cruncher USA Joined: Nov 1, 2006 Post Count: 85 Status: Offline Project Badges:
|
If you run the linux file command (file somefilename) does it show 64 bits? This has to be run on the actual OPN executable. On my Raspberry Pi 400, it is
/var/lib/boinc-client/projects/www.worldcommunitygrid.org/wcgrid_opn1_autodock_7.17_arm-unknown-linux-gnueabihf The file command shows this as ELF 32-bit ARM I would be interested in knowing what the file command shows for you. |
||
|
|
spRocket
Senior Cruncher Joined: Mar 25, 2020 Post Count: 280 Status: Offline Project Badges:
|
It does show up as 32-bit on mine as well. Looks like the 64-bit stuff is really only needed if you're running Rosetta@Home instead of WCG. R@H is a tight fit; it'll run four threads in 4 GB with zram instead of swap, but just barely.
|
||
|
|
|