Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 10
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 2091 times and has 9 replies Next Thread
KerSamson
Master Cruncher
Switzerland
Joined: Jan 29, 2007
Post Count: 1670
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Inaccurate estimated duration of C4CW WUs

Hi Everybody,
since a couple of days, two machines (currently mainly crunching for C4CW) received WUs with an estimated duration between 1 and 4 days each. Finally the WUs need between 2 and 8 hours.
Because I am running a small buffer (0.5 - 0.75 day), the waiting queue is very short (1 or 2 WU for 4 cores) and some of the WUs are running with high priority.
I would be interested to know if other members do currently experience the same behavior.
Cheers,
Yves
----------------------------------------
[Apr 15, 2012 7:54:36 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Inaccurate estimated duration of C4CW WUs

I have been running only c4cw and lately my est. times have been very consistent at 02:12:xx on one machine and 02:48:xx on the other.
The only time it ever varied is when I ran the HCC/GPU Beta's , and then it was all over the place...
But within a couple of days after it got right back to normal.

I wonder if it could have anything to do with the Boinc Manager version ?
I am running 6.10.58 for windows_x86_64
and 6.10.58 for x86_64-pc-linux-gnu
----------------------------------------
[Edit 1 times, last edit by Former Member at Apr 15, 2012 3:49:34 PM]
[Apr 15, 2012 8:21:58 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Zarozinia
Senior Cruncher
England
Joined: Aug 28, 2005
Post Count: 226
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Inaccurate estimated duration of C4CW WUs

Estimates are shot for me one is showing as 86 hours and one task that's taken 58 mins to complete 48% is showing as having 15 and a half hours to go.
----------------------------------------

[Apr 15, 2012 1:21:30 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Inaccurate estimated duration of C4CW WUs

smile
For the last few days, all my project estimates have been off by as much as a factor of 50. I think this has been caused by poor tuning of the March BOINC server upgrade.

Lawrence

added: Reported this to staff.
----------------------------------------
[Edit 1 times, last edit by Former Member at Apr 15, 2012 4:28:54 PM]
[Apr 15, 2012 4:18:34 PM]   Link   Report threatening or abusive post: please login first  Go to top 
TPCBF
Master Cruncher
USA
Joined: Jan 2, 2011
Post Count: 1931
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Inaccurate estimated duration of C4CW WUs

Don't see anything like this at all, and currently, beside three hosts additionally running CEP2, all my hosts are running C4CW exclusively and depending on the host, they show an estimated run time of 1.5-5h. All looking and acting just normal...

I did not mess with any buffer settings or such, all just plain installs of the stock WGC BOINC client...

Ralf
----------------------------------------

[Apr 15, 2012 5:25:42 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Bugg
Senior Cruncher
USA
Joined: Nov 19, 2006
Post Count: 271
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Inaccurate estimated duration of C4CW WUs

I also don't see this happening for me. Mine are all showing an estimated run time of around 48-50 minutes each.

Remember, if you run other projects with short run times, and it goes over even by, say, 30 minutes, that 30 minutes is a larger percentage of the estimated time, thus increasing all run time estimates by a larger factor.

There *IS* a way to reset your DCF, but it will eventually even itself out on its own if you just let it run without tinkering (running just one project will most likely even it out faster, btw).
----------------------------------------

i5-12600K (3.7GHz), 32GB DDR5, Win11 64bit Home

[Apr 16, 2012 12:09:54 AM]   Link   Report threatening or abusive post: please login first  Go to top 
littlepeaks
Veteran Cruncher
USA
Joined: Apr 28, 2007
Post Count: 748
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Inaccurate estimated duration of C4CW WUs

I've just been running C4CW lately. Most of my work units are showing an estimated run time of 1:32:10, and finishing in 1.53 to 1.56. That's a little bit over 1:32 -- I think that's about as good as it gets. wink
[Apr 16, 2012 1:53:34 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Zarozinia
Senior Cruncher
England
Joined: Aug 28, 2005
Post Count: 226
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Inaccurate estimated duration of C4CW WUs

Mine are still showing as estimated times of 61 hours, in reality they're taking a couple of hours.
----------------------------------------

[Apr 16, 2012 6:48:40 AM]   Link   Report threatening or abusive post: please login first  Go to top 
KerSamson
Master Cruncher
Switzerland
Joined: Jan 29, 2007
Post Count: 1670
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Inaccurate estimated duration of C4CW WUs

I thank you for your answers.
In between it seems that one host becomes accurate again by run time estimation, until the last one is still "crazy".
Cheers,
Yves
----------------------------------------
[Apr 16, 2012 10:38:26 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Inaccurate estimated duration of C4CW WUs

JmBoullier said that this happened to him recently when a HCMD2 work unit estimated at less than 4 minutes actually took more than 5 hours to run. Something like that probably happened to me.

blushing
Lawrence
[Apr 17, 2012 5:52:05 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread