| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Active Research
Forum: Mapping Cancer Markers Forum
Thread: Time variability |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 17
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Well I have just received 2 in a row with an estimated time of 45 - 50 hours !!! And only 7 days to finish.
I canceled the both immediately. It is not possible to finish them both in such a short time. Normally the estimated time was about 15 hours. I'm considering to stop participating this project. |
||
|
|
johncmacalister2010@gmail.com
Veteran Cruncher Canada Joined: Nov 16, 2010 Post Count: 799 Status: Offline Project Badges: 
|
Well I have just received 2 in a row with an estimated time of 45 - 50 hours !!! And only 7 days to finish. I canceled the both immediately. It is not possible to finish them both in such a short time. Normally the estimated time was about 15 hours. I'm considering to stop participating this project. Maybe you could sTay a while longer: your resources are needed here......  crunching, crunching, crunching. AMD Ryzen 5 2600 6-core Processor with Windows 11 64 Pro. AMD Ryzen 7 3700X 8-Core Processor with Windows 11 64 Pro (part time)  |
||
|
|
johnny000
Senior Cruncher Joined: Mar 3, 2014 Post Count: 150 Status: Offline |
I have had some work units state that they need a certain amount of time, but actually ended up needing much less.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Well I have just received 2 in a row with an estimated time of 45 - 50 hours !!! And only 7 days to finish. A week. Luxury! I had one which ended up around 600 credits. 40-50 hours. (Can't remember exactly, and it's not in my status screen any more.) It was a re-send, so only had a short deadline. I have had some work units state that they need a certain amount of time, but actually ended up needing much less. The only time I've seen that on MCM is when my DCF has been blown out by a huge job already. e.g. The job I mentioned above shot the DCF to over 3.6 so, yes, subsequent jobs had massively over-estimated work time. |
||
|
|
luispirela
Cruncher Joined: Sep 8, 2006 Post Count: 1 Status: Offline Project Badges: 
|
I am also having trouble with not enough time to complete MCM1 tasks. I have ended up cancelling several of them after being one or more days overdue. I have pumped up my CPU usage and have run my (work) computer on weekends and overnight in order to finish on time, but I cannot keep on babysitting this project. The developers need to adjust the task size. It is the only project on which I have had this problem. in most of them I finish well before the due time.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
What you do if a client struggles to complete work or is on irregular schedule is:
1. Set minimum work buffer fka connect every nn days to zero 2. Set maximum additional work buffer fka additional workbuffer to zero. When done the client only fetches work when a job has completed or is very near to completion. That's all there's to it. As for kremmen's problem, he runs on some ancient client of version 6 or before. The version 7 clients have dcf disabled by wcg. The factor remains 1, no adjusting from task to task. |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7850 Status: Offline Project Badges: 
|
I am also having trouble with not enough time to complete MCM1 tasks. I have ended up cancelling several of them after being one or more days overdue. I have pumped up my CPU usage and have run my (work) computer on weekends and overnight in order to finish on time, but I cannot keep on babysitting this project. The developers need to adjust the task size. It is the only project on which I have had this problem. in most of them I finish well before the due time. See Lavaflows answer above. Also lower your cache setting to 1 to 1.25 days. I have just had one of those monster jobs (44 hours) and it threw things out of whack for a while but on average the jobs seem to have stabilized in the 6 to 10 hour range on that particular machine. Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
|