No new units for days
1 Sep 2005 21:18:05 UTC
Topic 189822
(moderation:
I have had no new units for days, now Bonic says its idle. I run SETI as well but I know SETI are having problems at the moment, is Einstein down? It appears that each time I update I send a request for 0 minutes of work, this cant be right.
Andy
No new units for days
)
Reset the project...
If you need an Avatar, I'll create one for you!
Captain.Avatar-[at]-Gmail.com
This morning both SETI and
)
This morning both SETI and Einstein seem to have work units. I dont know what is happening but things seem to be working now.
Andy
RE: This morning both SETI
)
Andy – Possibly all your LTD (Long Term Debt) has elapsed and that’s why your client has resumed normal operations. Should such an occurrence happen in the future you can perform the following steps to perhaps correct the problem:
The aforementioned procedure was copied from this thread, and authored by Randy
_________________
Regards,
Tom
Theory of Gravitational Waves & LIGO
Laser Interferometer Space Antenna - LISA
JPL-Caltech
I would have thought
)
I would have thought regardless of his LTD, BOINC would grab something from somewhere rather then sit idle. At least I hope it would.
Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.
RE: I would have thought
)
Adrianxw – I’m not so sure that I’m in agreement with your posting, based on my understanding of LTD, as described in Paul’s Wiki at the following link, which outlines CPU scheduling of multi-projects within the BOINC Client.
Please take a look at the aforementioned link and offer your understanding(s). Should this link not come up properly the URL is:
http://boinc-doc.net/boinc-wiki/index.php?title=Long_Term_Debt
______________
Regards,
Tom
Theory of Gravitational Waves & LIGO
Laser Interferometer Space Antenna - LISA
JPL-Caltech
RE: I would have thought
)
It is supposed to. Unfortunately, in 4.45, there is a known bug that any work waiting to report is interpreted as in progress by this section of code. Thus, if (for example) if a host has completed all SETI work units, but can't connect, BOINC will sit idle instead of fetch work from Einstein with negative LTD. (This bug has been fixed in BOINC 4.72).
>>> I’m not so sure that I’m
)
>>> I’m not so sure that I’m in agreement with your posting
From the Wiki...
-----
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.
-----
... bolding added by me.
Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.
adrianxw – Point well taken,
)
adrianxw – Point well taken, and honestly at a lost for a reasonable explanation, to your quote from the WIKI, but my assumption was based on Andy’s first posting:
Which I have taken as “Andy’s SETI queue was totally empty”, but SETI would not accept his uploading of results (SETI out of commission for a number of days), hence his BOINC Client would not commit to additional work from another project such as Einstein. It would have been nice if we could have viewed the posted “error” messages from Andy’s client.
When SETI was back online and accepted Andy’s upload; this cleared the LTD, and Andy received work units from both E@H and S@H.
Your posting, of which I am in agreement with:
is correct with the overall assumption that the projects we are participating in are functionally operating properly and online for data transfers.
adrianxw, I’ll go back and do some more homework on this topic and hopefully someone else may be able to offer another opinion or clarification of our understandings of Andy’s posting.
Take Care,
Tom
Theory of Gravitational Waves & LIGO
Laser Interferometer Space Antenna - LISA
JPL-Caltech
Yes, I think nfortino has the
)
Yes, I think nfortino has the same point. It would seem that the failed uploads are still counted as in progress hence BOINC does not see the CPU as idle, although I would have thought it quite a simple matter to establish that the CPU time for example was not changing. That would also protect against stalled client apps.
I still run 4.25 as I don't like all this fiddling with the scheduler. I manage my machine better then BOINC ever will.
Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.
