| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Active Research
Forum: OpenPandemics - COVID-19 Project
Thread: Exaggerated runtime on android? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 11
|
|
| Author |
|
|
CaffeinatedSloth
Advanced Cruncher United Kingdom Joined: Nov 12, 2014 Post Count: 80 Status: Offline Project Badges: 
|
Hi all,
----------------------------------------I expected some of these WUs to take their time on android, and also understand that each task will vary in time due to the ligands being studied, etc. But I have 2 android phones (one quad-core and one octa-core) and the WUs have so far taken anywhere between 15-26 hours to complete (I don't know how this compares to other crunchers' stats). But of the ones I currently have running, some are looking like they'll take much longer than this - one is 38.2% through after 22:30, so the full WU will take close to 50-55 hours if it continues at that rate. Another is on 24.4% after 18 hours, suggesting it will take about 72 hours to fully complete! Is this normal behaviour for OPN on android? If it is, great - I'll just leave them crunching as they are, but if not I'll need to try and fix whatever's up with them. Cheers, Chris    |
||
|
|
yoerik
Senior Cruncher Canada Joined: Mar 24, 2020 Post Count: 413 Status: Offline Project Badges:
|
Hi all, I expected some of these WUs to take their time on android, and also understand that each task will vary in time due to the ligands being studied, etc. But I have 2 android phones (one quad-core and one octa-core) and the WUs have so far taken anywhere between 15-26 hours to complete (I don't know how this compares to other crunchers' stats). But of the ones I currently have running, some are looking like they'll take much longer than this - one is 38.2% through after 22:30, so the full WU will take close to 50-55 hours if it continues at that rate. Another is on 24.4% after 18 hours, suggesting it will take about 72 hours to fully complete! Is this normal behaviour for OPN on android? If it is, great - I'll just leave them crunching as they are, but if not I'll need to try and fix whatever's up with them. Cheers, Chris I have low to midrange android devices - all of them run over 20 hours for most MCM and OP WUs. However - that long a runtime suggests there might be issues with RAM? Each OP WU needs 250 MB each when it checkpoints - not having the necessary RAM available has caused it to fail to checkpoint. That could be why it's running so long?  |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The estimated runtimes on Android have proven to be a little off at times for me, but then this is particular while BOINC is still learning absent history. In one case saw 24 hours at 30 percent, yet it went from 60% to 100% in a minute.It just doesn't bother me in the least, they crunch when on juice and have so far finished 100% valid for me.
|
||
|
|
CaffeinatedSloth
Advanced Cruncher United Kingdom Joined: Nov 12, 2014 Post Count: 80 Status: Offline Project Badges:
|
One has 2gb RAM and has 4 tasks, the other has 3gb and has 8 tasks - that should be enough, right?
----------------------------------------There are some on both devices which are exhibiting a more normal run time of 20-25 hours predicted, so if it is RAM, it's only affecting approx 30-40% of the total tasks running on them. Chris |
||
|
|
CaffeinatedSloth
Advanced Cruncher United Kingdom Joined: Nov 12, 2014 Post Count: 80 Status: Offline Project Badges:
|
The estimated runtimes on Android have proven to be a little off at times for me, but then this is particular while BOINC is still learning absent history. In one case saw 24 hours at 30 percent, yet it went from 60% to 100% in a minute.It just doesn't bother me in the least, they crunch when on juice and have so far finished 100% valid for me. So it's possible that it's still just figuring out what the actual runtime should be? I've not had a single error or invalid from them so far, so not too worried from that side, I just wonder if there's anything to be done to speed them up? Chris |
||
|
|
yoerik
Senior Cruncher Canada Joined: Mar 24, 2020 Post Count: 413 Status: Offline Project Badges:
|
One has 2gb RAM and has 4 tasks, the other has 3gb and has 8 tasks - that should be enough, right? There are some on both devices which are exhibiting a more normal run time of 20-25 hours predicted, so if it is RAM, it's only affecting approx 30-40% of the total tasks running on them. Chris hmm. should be. Yeah - sorry I can't help more. No clue what's causing that. The only other thing I could think of is a hardware issue (your CPU is a weak boi, or there's a cooling issue --- idk tbh) I'm wasting your time by saying anymore lol. GL - I hope you figure it out. |
||
|
|
Tamagoch
Cruncher Ukraine Joined: Jul 21, 2007 Post Count: 35 Status: Offline Project Badges: 
|
android app is quite low in options - it's downloading job cache as much as it wants and then couldn't make it to fit in the deadline... it cannot use CPU in full (so much to read about it) and even with 50% cores in use the task affinity doesn't look optimal... android OS itself is not intended to use for high performance computing so I still don't believe in this part of BOINC and probably will uninstall the app again (
----------------------------------------a special android builds should be created for boinc or even Linux ARM distros to make it crunch at the best... but no one will do that because of the risk too much phones to be burnt and even more batteries could explode... I'm thinking of creating a 'smartphone crunching box' so people be able to utilize old phones safely with a scientific profit but a huge variety of devices makes almost impossible to create the universal solution like that... will leave it in mind for a future project ) [Edit 2 times, last edit by Tamagoch at May 19, 2020 5:34:11 AM] |
||
|
|
yoerik
Senior Cruncher Canada Joined: Mar 24, 2020 Post Count: 413 Status: Offline Project Badges:
|
android app is quite low in options - it's downloading job cache as much as it wants and then couldn't make it to fit in the deadline... it cannot use CPU in full (so much to read about it) and even with 50% cores in use the task affinity doesn't look optimal... Job cache can be limited by the amount of storage you give the app access to - and through Device Profiles on WCG. second option doesn't apply to other projects, but still. It's a simple way to throttle the queue - less confusing to the average user imo than the "x days + additional" system on pcs. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
It's much easier to size the queue by using the project level limits on the device profiles. My tablet runs 3 concurrent OPN1 and the profile is set to allow 4, so 1 should be waiting, were it not that I'm constantly seeing "Tasks are committed to other platforms", but only on Android (see separate threat). Yesterday set my phone up to run 1, and separate profile is set to sent 1, so that's what it's got. There's a small gap between finishing one and fetching the next, but that's OK. On 32 hours runtime, negligible.
|
||
|
|
CaffeinatedSloth
Advanced Cruncher United Kingdom Joined: Nov 12, 2014 Post Count: 80 Status: Offline Project Badges:
|
I've just set up another identical phone (HUAWEI P9 Lite) to see if there's anything that's different. Both are solely running BOINC 24/7 and are set to the same prefs. On the recent addition, it also seems to be expecting about 35-40 hours for a few WUs too. I do wonder if this is just how this phone copes with the different sizes of WU then, given that they are all different sizes... Like I said, I'm not too worried about it - it's just a shame that they're not running quite as fast as they possibly could.
----------------------------------------I tried limiting one of them to 6 cores for a while, but didn't notice a difference there... Chris |
||
|
|
|