| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: Outsmart Ebola Together
Thread: OET performance on Android devices |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 48
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Time for badges is CPU time on CPU jobs, Elapsed for GPGPU jobs [because there's no timekeeping on a GPGPU]. Elapsed is the time a job is allowed to run, Runtime is the time the job was actually computing [the cycles used by the science app]. Help overrules anything I wrote before, so here is the definitive: https://secure.worldcommunitygrid.org/help/viewSearch.do?searchString=elapsed
Here's a 1 page sample of my 4 core tablet, but only allowed to use 2 for stability reasons. Taking the first few, it looks like 95-96% efficiency i.e. if I don't touch the device, I'd get 2*24*.96 = ~1.9 days out of the tablet. OET1_ 0001059_ xSDGP-L_ rig_ 69663_ 0-- android_2654196 a Valid 7/31/15 01:42:16 7/31/15 17:48:56 3.31 / 3.48 18.7 / 18.7 OET1_ 0001059_ xSDGP-L_ rig_ 9350_ 0-- android_2654196 a Valid 7/30/15 21:37:17 7/31/15 17:35:58 5.26 / 5.48 29.8 / 29.8 OET1_ 0001055_ xSDGP-L_ rig_ 78786_ 4-- android_2654196 a Valid 7/30/15 17:04:16 7/31/15 14:20:21 8.39 / 8.64 49.1 / 46.3 OET1_ 0001058_ xSDGP-L_ rig_ 16411_ 0-- android_2654196 a Valid 7/30/15 17:35:42 7/31/15 12:07:05 4.90 / 5.06 28.9 / 28.9 OET1_ 0001058_ xSDGP-L_ rig_ 15631_ 0-- android_2654196 a Valid 7/30/15 12:20:00 7/31/15 07:03:38 5.09 / 5.22 29.6 / 29.6 OET1_ 0001056_ xSDGP-L_ rig_ 96344_ 2-- android_2654196 a Pending Validation 7/30/15 05:44:28 7/31/15 05:41:41 3.90 / 3.99 22.4 / 0.0 OET1_ 0001056_ xSDGP-L_ rig_ 57054_ 0-- android_2654196 a Valid 7/30/15 00:28:38 7/31/15 01:50:28 4.13 / 4.22 23.5 / 23.5 OET1_ 0001056_ xSDGP-L_ rig_ 88599_ 0-- android_2654196 a Valid 7/30/15 05:29:32 7/31/15 01:42:15 3.49 / 3.57 19.6 / 19.6 OET1_ 0001056_ xSDGP-L_ rig_ 10033_ 0-- android_2654196 a Valid 7/29/15 23:31:37 7/30/15 22:08:09 4.38 / 4.54 24.6 / 24.6 OET1_ 0001055_ xSDGP-L_ rig_ 78653_ 0-- android_2654196 a Valid 7/29/15 19:47:06 7/30/15 21:37:17 4.37 / 4.55 24.6 / 24.6 OET1_ 0001053_ xSDGP-L_ rig_ 14335_ 4-- android_2654196 a Pending Validation 7/29/15 04:38:53 7/30/15 00:28:37 5.23 / 5.36 32.4 / 0.0 OET1_ 0000647_ xZAGP-F_ rig_ 99675_ 3-- android_2654196 a Pending Validation 7/28/15 16:40:36 7/29/15 13:17:59 7.95 / 8.42 51.4 / 0.0 OET1_ 0001050_ xSDGP-L_ rig_ 47614_ 3-- android_2654196 a Valid 7/28/15 16:40:36 7/29/15 11:19:30 4.04 / 4.31 26.2 / 27.6 OET1_ 0001050_ xSDGP-L_ rig_ 28703_ 3-- android_2654196 a Pending Validation 7/28/15 15:54:56 7/29/15 06:58:51 2.26 / 2.33 13.7 / 0.0 OET1_ 0001050_ xSDGP-L_ rig_ 60251_ 4-- android_2654196 a Pending Validation 7/28/15 13:48:25 7/29/15 04:51:12 4.01 / 4.11 26.3 / 0.0 |
||
|
|
cristipurdel
Senior Cruncher Joined: Dec 13, 2008 Post Count: 158 Status: Offline Project Badges: 
|
Hmmm, I still do not understand why I get something like this for Android
----------------------------------------Pending Validation 7/24/15 05:07:45 7/26/15 08:21:56 11.92 / 49.44 43.6 / 0.0 and for Windows I get Pending Validation 7/28/15 15:04:49 7/29/15 04:30:03 9.10 / 9.27 43.2 / 0.0 So on Android I get an efficiency of 25% while for Windows I get 98% |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Get some apps like Battery Doctor and Clean Master. These will tell what's eating power and CPU time.
|
||
|
|
cristipurdel
Senior Cruncher Joined: Dec 13, 2008 Post Count: 158 Status: Offline Project Badges:
|
Are you using the official Boinc app or NativeBOINC?
----------------------------------------Your tablet has x86 or ARM processor? Maybe there is a connection somehow :) |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The basics:
----------------------------------------1) NativeBOINC does not install on Android 5.0+, it does not understand PIE memory management [I'm on official BOINC for Android from Berkeley]. 2) There's no x86 Android apps available, only ARM based [talking WCG only of course] As indicated -you- have to diagnose the device with tools as suggested as to what is using the other 75%. My setting is "Pause at [non-BOINC] CPU usage above 50%", i.e. the client pauses if I do other heavier stuff on the tablet. At that time the Elapsed time counting stops too. If you have high CPU use, but a low pause setting, the science just goes on counting Elapsed/Clock time, but does much less actual computing. That's what your results indicates... running but only computing [getting] ~25% of the time. [Edit 1 times, last edit by Former Member at Aug 2, 2015 9:10:38 AM] |
||
|
|
3A4scLiRhJVcdT2K9q9kQNxzxYJ9
Advanced Cruncher Joined: Nov 16, 2009 Post Count: 72 Status: Offline |
Hi folks... Nice hello from my holidays in greek island of "Kos" :) i noticed that my android devices that come with 8-core mediatek "mtk6752" running at 1.7ghz ask for 90-100 credit per unit(!) and being awarded that amount whilst my units running on mediatek "mtk6592" (8-core as well!) running at (slightly less) 1.4ghz only ask for 30-40 credits per units while being credited +50% of it because of average maths. Somethings not right there. Can someone forward that topic to the boinc agent dev team? I am having a greek beer to the health of all of you! Yiamas! (=cheers!)
----------------------------------------[Edit 1 times, last edit by SHOPXXL-COM at Aug 3, 2015 2:34:03 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
One mtk is on ouzo, the other on retsina ;P
(A topic that so decomposed, only the bones are left, will not be forwarded to the agent dev team... wasting my time, wasting everyone's time to do so, as the messages are auto-round archived. Until WCG indicate it will do something, that's the status quo AFAIC) [/ot] Ena potìri nerò, parakalò |
||
|
|
cristipurdel
Senior Cruncher Joined: Dec 13, 2008 Post Count: 158 Status: Offline Project Badges:
|
The basics: 1) NativeBOINC does not install on Android 5.0+, it does not understand PIE memory management [I'm on official BOINC for Android from Berkeley]. 2) There's no x86 Android apps available, only ARM based [talking WCG only of course] As indicated -you- have to diagnose the device with tools as suggested as to what is using the other 75%. My setting is "Pause at [non-BOINC] CPU usage above 50%", i.e. the client pauses if I do other heavier stuff on the tablet. At that time the Elapsed time counting stops too. If you have high CPU use, but a low pause setting, the science just goes on counting Elapsed/Clock time, but does much less actual computing. That's what your results indicates... running but only computing [getting] ~25% of the time. When I am running on one core efficiency is near 100%, I have tested on a 2nd mobile. When I use 2 or more cores, efficiency is around 50%, and for 3 cores is like 33%. On both devices I get more or less the same outcome. Could it be then when it goes into sleeping mode, only 1 core is awake? Does anyone see the same behavior on smartphones, not rooted, with boinc official and non-Lollipo version? Found also this link from boinc forums I will further test with nativeBOINC and root ---------------------------------------- [Edit 1 times, last edit by cristipurdel at Aug 4, 2015 6:01:57 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Very well possible the CPU switches to some lower allocation / threads and then runs 2/3/4 threads really on 1 core. Could also be there are hyperthreaded kind of mobiles around... the more run, the lower the CPU allocation. Elapsed is just what it is, recording time the app is allowed to run. At any rate, "Pause computation when screen is on" was one of the first things I've unticked, to make sure the device does not go to sleep, just the display is powered down after 3 minutes of not touching [system settings, but crunching continues full throttle.
|
||
|
|
NixChix
Veteran Cruncher United States Joined: Apr 29, 2007 Post Count: 1187 Status: Offline Project Badges: 
|
The problem that I am having is that the time between checkpoints is longer that my Android can run without being interruped. I have watched jobs ping-pong between two amounts of run time. Its at 12 hours, then back to 10. I might as well remove them from my pool of crunchers. OET may run on Android, but it is doing a poor job of it.
----------------------------------------Cheers   |
||
|
|
|