Hi all,

it\'s now one month in a row that my Client is crunching CPDn and only that. I mean, I have other projects attached, but since one month, no matter what I try, any communication I force them to have with their schedulers, BOINC reports the \"... |Note: not requesting new work or reporting results\" message.
Reading other posts, I can suppose this is something related to CPDN being in debt (though I don\'t understand that very much). But, isn\'t one month of crunching enough? And why isn\'t there any \"blinking light\" showing such a condition (i.e., shouldn\'t BOINC say something like \"not downloading anything else because U mistreated this project and I, The Client, am now making justice!\")?


27/01/2006 7.32.52||Starting BOINC client version 5.2.13 for windows_intelx86
27/01/2006 7.32.52||libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3
27/01/2006 7.32.52||Data directory: D:\\Programmi\\BOINC
27/01/2006 7.32.58||Processor: 1 GenuineIntel Intel(R) Pentium(R) M processor 1.73GHz
27/01/2006 7.32.58||Memory: 503.36 MB physical, 1.20 GB virtual
27/01/2006 7.32.58||Disk: 22.47 GB total, 127.00 MB free
27/01/2006 7.32.59|rosetta@home|Computer ID: 64793; location: home; project prefs: default
27/01/2006 7.32.59|boincsimap|Computer ID: 1348; location: home; project prefs: default
27/01/2006 7.32.59|BURP|Computer ID: 9693; location: home; project prefs: default
27/01/2006 7.32.59|climateprediction.net|Computer ID: 291202; location: home; project prefs: default
27/01/2006 7.32.59|LHC@home|Computer ID: 74355; location: home; project prefs: default
27/01/2006 7.32.59|Predictor @ Home|Computer ID: 176013; location: home; project prefs: default
27/01/2006 7.32.59|SETI@home|Computer ID: 1700312; location: work; project prefs: default
27/01/2006 7.32.59|SETI@home Beta Test|Computer ID: 2933; location: home; project prefs: default
27/01/2006 7.32.59|uFluids|Computer ID: 2801; location: home; project prefs: default
27/01/2006 7.32.59||General prefs: from climateprediction.net (last modified 2005-12-30 15:38:25)
27/01/2006 7.32.59||General prefs: no separate prefs for home; using your defaults
27/01/2006 7.33.00||Remote control not allowed; using loopback address
27/01/2006 7.33.00|climateprediction.net|Resuming computation for result sulphur_el51_000680581_0 using sulphur_cycle version 422

---

Based on the stats for your host 291202 I calculate from the result\'s average secs/TS that it has around 1044 hours to go. That\'s 43.5 days, and the result has a deadline of 19 Nov 2006. That deadline could be met if BOINC was running CPDN for 3.5 hours a day. Your trickle history suggests that it\'s running a lot more than that (although it does appear that the model is slowing down from the way the secs/TS seems to be increasing), so I can\'t immediately understand why CPDN is running to the exclusion of the other 8 projects you\'re connected to.

While the system\'s running like this the other projects should be building up a large debt. You should find that CPDN doesn\'t download a new workunit for a few months after the current one is completed.

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

quote:
And why isn\'t there any \"blinking light\" showing such a condition (i.e., shouldn\'t BOINC say something like \"not downloading anything else because U mistreated this project and I, The Client, am now making justice!\")?

There\'s no light because Justice is blind. :)

***********

quote:
... related to CPDN being in debt (though I don\'t understand that very much).

There are a lot of links on <a href=\"http://boinc-doc.net/boinc-wiki/index.php?search=debt&go=Go\"> this</a> page of the BOINC Wiki on \'debt\'.

That deadline could be met if BOINC was running CPDN for 3.5 hours a day. Your trickle history suggests that it\'s running a lot more than that (although it does appear that the model is slowing down from the way the secs/TS seems to be increasing), so I can\'t immediately understand why CPDN is running to the exclusion of the other 8 projects you\'re connected to.

While the system\'s running like this the other projects should be building up a large debt. You should find that CPDN doesn\'t download a new workunit for a few months after the current one is completed.

Exctly the same considerations I made... That doesn\'t sound like an optimised behaviour for the scheduler, though.

Thanks to both for your replies.

---

That doesn\'t sound like an optimised behaviour for the scheduler, though.

The answer seems to lay in-between these lines found in the Boinc Wiki:

Long Term Debt
Long term debt is part of the decision of which project to download from next. If the long term debt is less than negative Queue Size no work request will be made of that project unless a CPU is idle. Long term debt is shifted such that the mean is always 0 (the sum of all Long Term Debt values is 0).

I happened to suspend CDPN many times, and this could have brought such a condition. The problem I see, however, is that I did it with a much slower PC (400Mhz), and the debt is calculated in seconds. So, IMHO, it would be better to have debt managed for every host rather than globally for the user account - as it seems to have done on this case. Otherwise, since numbers crunched per time varies witth the speed of the computer, debt could still be calculated globally for the single user, but based on the effective crunching rather than on time (i. e., on the credit given - but this colud be a problem for WUs with errors - or on the \"time\" ratioed the result of the benchmarks).

And, I repeat, it SHOULD say something! ;op

---

This is the sort of discussion that would be more likely to \'bear fruit\' on the <a href=\"http://boinc.berkeley.edu/dev/\"> BOINC boards,</a> where ideas for changes are regularly discussed.

LTD is calculated on a per host basis. No server interactions.

---

BOINC WIKI

BOINCing since 2002/12/8

This is the sort of discussion that would be more likely to \'bear fruit\' on the <a href=\"http://boinc.berkeley.edu/dev/\"> BOINC boards,</a> where ideas for changes are regularly discussed.

Les,

do you know a neat way to do that (something like \"move discussion to other forum\"? Re-writing, or also writing a \"pointer\" on the other forum, doesn\'t seem one...

---

Sorry, different country.
This forum is at Oxford uni, England.
BOINC is at Berkeley, Uni. of California, USA.

So, you have to start again.

Thread continued <a href=\"http://boinc.berkeley.edu/dev/forum_thread.php?id=555\"> here.</a>