BOINC Android trying to run 4 Rosetta WU when device doesn't have enough RAM.

Message boards : Number crunching : BOINC Android trying to run 4 Rosetta WU when device doesn't have enough RAM.

To post messages, you must log in.

AuthorMessage
marmot

Send message
Joined: 10 Nov 15
Posts: 16
Credit: 125,724
RAC: 0
Message 90481 - Posted: 5 Mar 2019, 22:39:49 UTC
Last modified: 5 Mar 2019, 22:42:59 UTC

Stats on device:

ARMv7 Processor rev 3 (v7l) 4 core
Android 3.10.54+ (Android 5.1.1)
BOINC version 7.4.53
Memory 867.21 MB
Swap space 64 MB
Free Disk Space 1.96 GB

BOINC set to use 80% available RAM (642 MB).

Work units report:
rb_02_26_1337_1484_ab_t000__robetta_cstwt_5.0_IGNORE_THE_REST_07_16_818652_18_0
Work Unit: 955067857
Peak working set size 422.19 MB
Peak swap size 645.55 MB
Peak disk usage 579.42 MB

Stderr:
WARNING: linker: ../../projects/boinc.bakerlab.org_rosetta/rosetta_android_4.10_arm-android-linux-gnu: unused DT entry: type 0x6ffffffe arg 0x26cc
WARNING: linker: ../../projects/boinc.bakerlab.org_rosetta/rosetta_android_4.10_arm-android-linux-gnu: unused DT entry: type 0x6fffffff arg 0x2
(these two lines repeat 256 times)
Too many restarts with no progress. Keep application in memory while preempted.
======================================================
DONE :: 1 starting structures 25076.7 cpu seconds
This process generated 1 decoys from 1 attempts
======================================================
BOINC :: WS_max 0
called boinc_finish(0)

-------------------------
There is another invalid WU like this that hit the 512 error limit and another that completed (because I manually forced one Rosetta into RAM by suspending Rosetta, d/ling WCG Zika, starting them, unsuspending Rosetta, then suspending individual Zika till a single Rosetta was running). Why doesn't Rosetta Android WU have a suspension control?!?!

BOINC attempted to run 4x of these work units, with 360-412MB working sets, at once in a device with 642MB RAM available to BOINC.

Something is wrong here....

I could have easily bypassed this bug if Rosetta ARM WU came with a manual suspension control.
Suspending 3 of the 4 WU's and let them complete 1 at a time while another project got the other 3 cores.

Is this the fault of BOINC ARM or is Rosetta WU not properly reporting its needed RAM to BOINC so that BOINC can properly manage the WU count? Or is it because BOINC isn't able to properly suspend Rosetta WU's (tied to the lack of manual suspend control)?

This tablet put in 70,000 hours on Universe BH SPin2 over the last 2 years.
I'd love to have given some of that time to Rosetta.
ID: 90481 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
marmot

Send message
Joined: 10 Nov 15
Posts: 16
Credit: 125,724
RAC: 0
Message 90484 - Posted: 6 Mar 2019, 7:07:17 UTC - in response to Message 90481.  


I could have easily bypassed this bug if Rosetta ARM WU came with a manual suspension control.


The suspension (pause icon) control is showing on this final WU.
The only control showing when Rosetta for Android was attempting 4 at once was to abort (stop icon).
ID: 90484 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Profile David E K
Volunteer moderator
Project administrator
Project developer
Project scientist

Send message
Joined: 1 Jul 05
Posts: 1016
Credit: 3,974,123
RAC: 310
Message 90497 - Posted: 8 Mar 2019, 16:32:03 UTC

Can you configure R@h to use only 1 cpu for your device and see if that helps?
ID: 90497 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
marmot

Send message
Joined: 10 Nov 15
Posts: 16
Credit: 125,724
RAC: 0
Message 90499 - Posted: 9 Mar 2019, 6:46:55 UTC - in response to Message 90484.  


I could have easily bypassed this bug if Rosetta ARM WU came with a manual suspension control.


The suspension (pause icon) control is showing on this final WU.
The only control showing when Rosetta for Android was attempting 4 at once was to abort (stop icon).


Update 2: So when BOINC is running under incredibly low RAM circumstances; it's GUI misreports many things.

It showed the WU's were running (they were not), then it showed they were paused (they were running sporadically according to Kernel Auditor) and then that it was suspended till the battery reached 30% (current battery level 96%).

The lack of pause icon/control menu was just a misreporting aberration.

------
Can you configure R@h to use only 1 cpu for your device and see if that helps?


I'm sure that if I create an app_config.xml with <project_max_concurrent>1</..> it will help; just BOINC, with reporting from the Rosetta WU, should have pause WU's based on available RAM and that didn't happen.
ID: 90499 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
marmot

Send message
Joined: 10 Nov 15
Posts: 16
Credit: 125,724
RAC: 0
Message 90741 - Posted: 2 May 2019, 19:23:15 UTC - in response to Message 90497.  

Can you configure R@h to use only 1 cpu for your device and see if that helps?


Set project_max_concurrent to 2.

Just wanted to point out that it requires a rooted tablet/phone to access the (root)/data/data/edu.berkeley.boinc/client/projects/boinc.bakerlab.org_rosetta folder.

Decent file manager, that allows creation of a new file from scratch then has a built in text editor that didn't add any hidden characters, is alc' s "File Manager'.
Think you probably need to set permissions to rw-r-r before use.

Then reboot or force stop the app with settings_>apps (unless I missed the menu command to reread config files; looked for it).
Event Log should say Rosetta@home found app_config.
If errors are found in the app_config then you'll get red text after that statement.


All that work... no Android WU's :(
ID: 90741 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote

Message boards : Number crunching : BOINC Android trying to run 4 Rosetta WU when device doesn't have enough RAM.



©2019 University of Washington
http://www.bakerlab.org