Sat 23 Apr 2016 10:20:20 PM UTC | | Benchmark results:
Sat 23 Apr 2016 10:20:20 PM UTC | | Number of CPUs: 4
Sat 23 Apr 2016 10:20:20 PM UTC | | 1005 floating point MIPS (Whetstone) per CPU
Sat 23 Apr 2016 10:20:20 PM UTC | | 3506 integer MIPS (Dhrystone) per CPU
With cpus running at 1.15GHz, with some temporary drops to 1.10GHz.
The question is which projects provide arm64 binaries for they work.
If you are using Debian or Ubuntu based distro, and want to join SETI@Home, just install boinc-app-seti package. It will make boinc-client use it automatically
pine64user@debianpine64:/var/lib/boinc-client$ ps aux | grep seti
boinc 23364 97.8 3.5 89668 72972 ? RNl 22:29 2:59 ../../projects/setiathome.berkeley.edu/setiathome_v8
pine64user@debianpine64:/var/lib/boinc-client$ file projects/setiathome.berkeley.edu/setiathome_v8
projects/setiathome.berkeley.edu/setiathome_v8: symbolic link to /usr/lib/boinc-app-seti/setiathome_v8
$ file -L /var/lib/boinc-client/projects/setiathome.berkeley.edu/setiathome_v8
/var/lib/boinc-client/projects/setiathome.berkeley.edu/setiathome_v8: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, BuildID[sha1]=7ff21f252684c89976528b28922eca4f79b208e2, stripped
It looks it will finish my work unit in about 36 hours. I know RPI2 is doing about 77h per WU.
Still this is only at one core, with 1.15GHz. Will see how things heat up with 4 WUs in progress and 4 cores busy. I do have small heatsink, but it might become a bit warm.
It looks every instance of setiathome_v8 uses about 80MB of RES memory. The application itself is small (3MB shared memory).
Sat 23 Apr 2016 10:20:20 PM UTC | | Number of CPUs: 4
Sat 23 Apr 2016 10:20:20 PM UTC | | 1005 floating point MIPS (Whetstone) per CPU
Sat 23 Apr 2016 10:20:20 PM UTC | | 3506 integer MIPS (Dhrystone) per CPU
With cpus running at 1.15GHz, with some temporary drops to 1.10GHz.
The question is which projects provide arm64 binaries for they work.
If you are using Debian or Ubuntu based distro, and want to join SETI@Home, just install boinc-app-seti package. It will make boinc-client use it automatically
pine64user@debianpine64:/var/lib/boinc-client$ ps aux | grep seti
boinc 23364 97.8 3.5 89668 72972 ? RNl 22:29 2:59 ../../projects/setiathome.berkeley.edu/setiathome_v8
pine64user@debianpine64:/var/lib/boinc-client$ file projects/setiathome.berkeley.edu/setiathome_v8
projects/setiathome.berkeley.edu/setiathome_v8: symbolic link to /usr/lib/boinc-app-seti/setiathome_v8
$ file -L /var/lib/boinc-client/projects/setiathome.berkeley.edu/setiathome_v8
/var/lib/boinc-client/projects/setiathome.berkeley.edu/setiathome_v8: ELF 64-bit LSB shared object, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, BuildID[sha1]=7ff21f252684c89976528b28922eca4f79b208e2, stripped
It looks it will finish my work unit in about 36 hours. I know RPI2 is doing about 77h per WU.
Still this is only at one core, with 1.15GHz. Will see how things heat up with 4 WUs in progress and 4 cores busy. I do have small heatsink, but it might become a bit warm.
It looks every instance of setiathome_v8 uses about 80MB of RES memory. The application itself is small (3MB shared memory).