Hi everyone,

As I'm sure was noticed, there's a 2nd version of the "xoroshigo" project denoted by v1.1.
This new version has had changes made to its input variables that made it incompatible with the old version, so we could not run it as an updated version of the same app.

That being said, after extensive testing, we've deployed v1.02 of xoroshigo2(or v1.1.1.02, depending on who you ask) to production.
I believe there should also be a potential fix for the issue where work would not suspend when changes are made to computing preferences or work is just simply suspended.

The most notable change is that a member of our team, Andrew, developed a port of one of the most expensive functions (95+% of execution time spent in this function) used in the app to run it as native code for a 20x speedup.
We've cranked the dials, so tasks should be roughly the same size as before, but you may experience runtime variances compared to before. Overall this just means you're completing 20x what you used to in the same amount of time (cheaper on compute resources) - so the credit values are remaining the same.

There is also now an aarch64 build of this app available. We've made best efforts to test this with our limited aarch64 machines, so if any issues are encountered, please let us know.

Finally, I wanted to mention that as of now, we're enforcing a GLIBC 2.17 or above requirement for our apps going forward. I've built a lot of CI test harnesses over the last day or two that allow me to detect issues before they ever hit BOINC, and while I had been doing this already, there is now a check on our internal repo preventing any merges with binaries with a GLIBC over 2.17. This does also mean you'll need GLIBC 2.17 or higher to run the apps we build going forward.

Anyway, happy crunching! As always, please let us know if you run into any issues.

One last note:

I've disabled scheduling work for the old version, as I haven't seen any errors in the new build of v1.1.
Since we get ~20x the output out of v1.1 compared to v1.0, I want to prioritize that going forward.

Quick question: How much RAM needs your aarch64 build per thread?

Just a min or so in but it seems about the same as the old app, My first task on a RPI3b is 94m according to BOINCTasks.

Is this the permanent end to the 1.0 app? Since v1.1 was named differently it counts separately for WUProp hours.

I intended to sunset the 1.0 app since the 1.1 app is significantly more efficient on resources (which we utilize to complete more work per work unit than before, but with fewer resources than 1.0, so the credit values are the same).

If the community wants to continue crunching on 1.0 too I guess I could add it back in.

Ideally they wouldn’t be separate apps at all. It’s just problematic because the input vars changed and there isn’t really a way to keep the new binary from running old tasks.


I suppose an alternative solution would be to wait for all outstanding 1.0 tasks to complete, then cancel the rest, merge 1.1 back into 1.0’s app, then generate more work using 1.0’s app (which at that point has been replaced by 1.1).

Anyway I’m open to ideas. Does the community want to continue crunching 1.0 until such time as I can merge 1.1 back in?

Quick question: How much RAM needs your aarch64 build per thread?

175MB per task on my devices

just release the remaining 1.0 tasks, let them complete but don't create any more - there aren't many and it will tidy itself up

Tasks with this text in the name hixorlo or regular = ~95mb. Those with hxlreg = ~175mb.

it took me 2,7h/WU with 2C on a phone, not bad https://minecraftathome.com/minecrafthome/result.php?resultid=11577728

is Android support planned?

just release the remaining 1.0 tasks, let them complete but don't create any more - there aren't many and it will tidy itself up

+1 for what Vato has said

This is all that is needed to be done boysanic and it will clean things up without further intervention.

Conan

Better than my RPI 3B at about 5 hours with 9 more to go (estimated 14 hours)

Edit: Moved this post to the following thread, as requested:

https://minecraftathome.com/minecrafthome/forum_thread.php?id=207