1) Message boards : News : New ATLAS app version released for Linux hosts (Message 35489)
Posted 12 Jun 2018 by Profile Joe's Collider
I don't know if this helps much since I don't know what your code uses, and you might already be doing this now...
Reading the original post, reminded me about LSB (Linux Standard Base), and limiting your code to calling only what's in LSB that would give you a larger audience.
Here's information on LSB: https://refspecs.linuxfoundation.org/lsb.shtml
...if you're already doing this, ignore this reply.

...under the same thoughts, this may also help: https://en.wikipedia.org/wiki/C_standard_library
2) Message boards : Sixtrack Application : i686 instead of x86_64: why? (Message 28803)
Posted 6 Feb 2017 by Profile Joe's Collider
Many BOINC projects make most of their use with the floating point processor(s). You could think of this as a separate processor (like in the days of the 386CPU & 387FPU). Or in today's world, making use of the hundreds of FPUs in graphics cards to crunch in 30 seconds, something that would be hours on a generic CPU.

The rest of the program could be thought of as file handling and moving the results into/out_of files - although it may make a larger portion of the program, very little time is expected to be used there - I would not expect large speed gains comparing 32 and 64 bit code.

...I've got a low score, but I'm just contributing (otherwise) wasted CPU cycles to science :-)

©2020 CERN