Work generation suspended
There is a problem with the last application
The work generation is suspended for a few days.
Work generation suspended
There is a problem with the last application
The work generation is suspended for a few days.
. . . . . ___
. . . . . . .\___/\______
. . . . . . .\__AMD___\
\__
---------------------------------------------
WUProp client is fixed and is back to work now in version 3.26
. . . . . ___
. . . . . . .\___/\______
. . . . . . .\__AMD___\
\__
---------------------------------------------
Thank goodness for quick fixes... my machines were missing it![]()
2009 MULTI CORES CONTEST STATS
http://neogen.amdusers.com/contest2009/contestoverall.htm
CHRISTMAS QUEST CONTEST STATS
http://neogen.amdusers.com/contest2008/xmascontest.htm
http://neogen.amdusers.com/contest2008/stats.png (snapshot)
FEBRUARY '08 RACE STATS
http://neogen.amdusers.com/contest2008/racefeb08b.htm
http://neogen.amdusers.com/contest2008/racefeb08nb.htm
I have just downloaded yet another version: 3.27 Takes almost 60 hours to complete! nci, so I am not bothered by that, just hope that it is worth the effort, credit-wise.
After 1 hour it is 36% finished, looks like a very bad guestimate, the original 59+ hours. On my AMD Socket 754 system (my last true single-core) it even loads down as 73 hour WU, but 23 minutes running and it is 13% done.
Last edited by Dirk Broer; 10-01-2011 at 02:44 PM. Reason: 1 hour report
Yea... boinc tends to give some very off estimates in many projects... but it has its learning curve and after a good number of workunits it gets it right.![]()
2009 MULTI CORES CONTEST STATS
http://neogen.amdusers.com/contest2009/contestoverall.htm
CHRISTMAS QUEST CONTEST STATS
http://neogen.amdusers.com/contest2008/xmascontest.htm
http://neogen.amdusers.com/contest2008/stats.png (snapshot)
FEBRUARY '08 RACE STATS
http://neogen.amdusers.com/contest2008/racefeb08b.htm
http://neogen.amdusers.com/contest2008/racefeb08nb.htm
The high initial estimates are deliberate.
This is to prevent a newly attached client from getting flooded with work.
The estimate comes down very quickly as more work is completed and the BOINC core revises the estimates downwards based on actual completion times.
[edit- oops - NeoGen already said that, a bit more economically too. -edit]
. . . . . ___
. . . . . . .\___/\______
. . . . . . .\__AMD___\
\__
---------------------------------------------
2009 MULTI CORES CONTEST STATS
http://neogen.amdusers.com/contest2009/contestoverall.htm
CHRISTMAS QUEST CONTEST STATS
http://neogen.amdusers.com/contest2008/xmascontest.htm
http://neogen.amdusers.com/contest2008/stats.png (snapshot)
FEBRUARY '08 RACE STATS
http://neogen.amdusers.com/contest2008/racefeb08b.htm
http://neogen.amdusers.com/contest2008/racefeb08nb.htm
I've been running WuProp for a long time now, why way-off estimates all of a sudden?
I do not see a learning curve either, they keep getting bigger (the estimates)
And you can only do one at a time, so your PC cannot be flooded with WuProp WUs, no matter what.
Hi Dirk.
You are correct that the WUProp project sends only one work unit per client at a time.
It is possible that the estimate baseline was reset when the latest client app was released on 29 Sept.
http://wuprop.boinc-af.org/apps.php
The original WUProp work units ran for much longer than the current length.
You also observe that the estimate is getting longer.
I can confirm that I see the same thing on my clients also.
That behaviour is a puzzle.
There could be some other reason that the Admin may share with us?
http://wuprop.boinc-af.org/forum_reply.php?thread=129
. . . . . ___
. . . . . . .\___/\______
. . . . . . .\__AMD___\
\__
---------------------------------------------
Looks like my estimates are coming down again.
They exceeded 90 hours this morning, but now are back down to around 34 hours.
. . . . . ___
. . . . . . .\___/\______
. . . . . . .\__AMD___\
\__
---------------------------------------------