Client doesn't get enough tasks

Questions and Answers : Android : Client doesn't get enough tasks
Message board moderation

To post messages, you must log in.

AuthorMessage
vtarasov

Send message
Joined: 26 May 15
Posts: 4
Credit: 92,144
RAC: 0
Message 6583 - Posted: 13 Jun 2015, 4:46:14 UTC

On my Nexus 4, job cache is around 24 tasks, but only 12 tasks on (more powerful) Nexus 7. The log says "Not requesting tasks: don't need (job cache is full)". Despite having "download work for 10 days" in project preferences, my Nexus 7 tablet has work for just one day (no internet connection - no work to do).
How do I fix that?

Also, I noticed that Nexus 7 has smaller Gflops rating (application details->average processing rate) compared to Nexus 4 computer, which is ridiculous, and maybe that is the reason behind job cache size difference. How do I update that number? There isn't even a button to remove/delete a computer from my account!
ID: 6583 · Rating: 0 · rate: Rate + / Rate - Report as offensive
mikey
Avatar

Send message
Joined: 22 Jun 11
Posts: 2063
Credit: 1,000,866,048
RAC: 0
Message 6584 - Posted: 13 Jun 2015, 11:03:27 UTC - in response to Message 6583.  

There isn't even a button to remove/delete a computer from my account!


Lots of questions...I will tackle this one...go into your account on the website, then view computers on this account, then select the computer you want to delete and click details, as long as ALL tasks are returned, credited and the database says it's okay the delete this computer option will be highlighted at the bottom of the page. BUT if you have any workunits that have not cleared yet that option will not be available yet.
ID: 6584 · Rating: 0 · rate: Rate + / Rate - Report as offensive
vtarasov

Send message
Joined: 26 May 15
Posts: 4
Credit: 92,144
RAC: 0
Message 6589 - Posted: 15 Jun 2015, 20:09:29 UTC - in response to Message 6584.  

I apologise for a convoluted explanation :-) I guess my question is, how do I increase job cache size, so that my Nexus 7 is not idling without work to do?
ID: 6589 · Rating: 0 · rate: Rate + / Rate - Report as offensive
mikey
Avatar

Send message
Joined: 22 Jun 11
Posts: 2063
Credit: 1,000,866,048
RAC: 0
Message 6590 - Posted: 16 Jun 2015, 11:36:20 UTC - in response to Message 6589.  

I apologise for a convoluted explanation :-) I guess my question is, how do I increase job cache size, so that my Nexus 7 is not idling without work to do?


I don't know, I thought it was under your account, computing preferences, but it says for all devices EXCEPT and it lists Android Devices. So maybe they are adjusted on the device itself?
ID: 6590 · Rating: 0 · rate: Rate + / Rate - Report as offensive
Profile Teemu Mannermaa
Project administrator
Project developer
Project tester

Send message
Joined: 20 Apr 11
Posts: 381
Credit: 822,356,221
RAC: 11,452
Message 6634 - Posted: 6 Jul 2015, 13:17:48 UTC - in response to Message 6583.  

On my Nexus 4, job cache is around 24 tasks, but only 12 tasks on (more powerful) Nexus 7. The log says "Not requesting tasks: don't need (job cache is full)".


I tried to find the setting myself too and failed. I guess BOINC devs think it's too advanced for Android users or something. :(

It's true that the normal computing prefs are not used by Android devices, they only listen to locally configured settings and they are quite limited (one can't even setup remote management). NativeBOINC does have more normal configuration options but it's BOINC Client version is getting old.

It's the BOINC Client that says "job cache is full" and it's purely a client decision to fetch or not fetch work. BOINC Server or stats stored on serve side doesn't have much (or maybe anything) to do with the decision.

Also, I noticed that Nexus 7 has smaller Gflops rating (application details->average processing rate) compared to Nexus 4 computer, which is ridiculous, and maybe that is the reason behind job cache size difference. How do I update that number?


These are calculated based on the results received from the device. I don't think BOINC Client gets to even see these values as they are used by the BOINC Server to send work and to calculate granted credits. (Except we don't use that crediting option since it's unreliable but grant fixed amount instead.)

The only way to change these is to.. complete more work units successfully and the stats will change. Slowly but surely, if the new measurements are different. However, the measured GFLOPS might be affected by our apps CPU usage calculation bug where only CPU usage from last run is returned. This affects especially your Nexus 4 device as it pauses and restarts a lot. However, that shouldn't affect the average return time which is also quite different.

Do you still have this problem or did you find a way to fix it?

-w
ID: 6634 · Rating: 0 · rate: Rate + / Rate - Report as offensive
vtarasov

Send message
Joined: 26 May 15
Posts: 4
Credit: 92,144
RAC: 0
Message 6698 - Posted: 8 Sep 2015, 1:15:37 UTC - in response to Message 6634.  

I still have this problem: my Nexus 7 only downloads at most 11 tasks, and it's barely enough for 12 hours of work. After that, the table is idling, because it doesn't have a permanent internet connection to fetch more work.
ID: 6698 · Rating: 0 · rate: Rate + / Rate - Report as offensive
vtarasov

Send message
Joined: 26 May 15
Posts: 4
Credit: 92,144
RAC: 0
Message 6705 - Posted: 11 Sep 2015, 4:30:39 UTC - in response to Message 6698.  

I found a workaround that kind of works for my particular scenario.
I'm running dnetc client directly on Nexus 7, without a wrapper. Typically that would be a problem, because the client itself doesn't know current battery temperature and state of charge, and on my non-rooted Nexus 7 it doesn't detect if it's running on battery or is plugged in.
The tablet is a bit overheated, but because it's always plugged in, overall it works much better for me than the moowrap: I'm in control of dnetc.ini file and I'm manually setting work fetch threshold.
ID: 6705 · Rating: 0 · rate: Rate + / Rate - Report as offensive

Questions and Answers : Android : Client doesn't get enough tasks


 
Copyright © 2011-2019 Moo! Wrapper Project