| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: FightAIDS@Home Phase 2
Thread: FightAIDS@Home - Phase 2 AsyncRE work units started |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 47
|
|
| Author |
|
|
hchc
Veteran Cruncher USA Joined: Aug 15, 2006 Post Count: 746 Status: Offline Project Badges: 
|
Terribly sorry, but a day for a WU is too short. Trying to run this project is a waste of my resources. Starting a thread, and getting it bounced before it completes does nobody any good. I’ve only got a 1st gen core i7. Please extend a day to something sensible like five days. I agree! One day is way too short. I have a Core 2 Duo from 2007 and another Core 2 Duo on this project, and I've gotten it to work by adjusting my buffer to 0.01 days (and storing 0 additional days). So even if a WU takes 14 hours, I still return it in time. I wish the "1 WU per core" limit were raised so that we can participate 100% in this project instead of alternating between FAAH2 and other projects. Even 1 WU per core + 1 WU would allow this to work.
|
||
|
|
pcwr
Ace Cruncher England Joined: Sep 17, 2005 Post Count: 10903 Status: Offline Project Badges: 
|
Terribly sorry, but a day for a WU is too short. Trying to run this project is a waste of my resources. Starting a thread, and getting it bounced before it completes does nobody any good. I’ve only got a 1st gen core i7. Please extend a day to something sensible like five days. I agree! One day is way too short. I have a Core 2 Duo from 2007 and another Core 2 Duo on this project, and I've gotten it to work by adjusting my buffer to 0.01 days (and storing 0 additional days). So even if a WU takes 14 hours, I still return it in time. I wish the "1 WU per core" limit were raised so that we can participate 100% in this project instead of alternating between FAAH2 and other projects. Even 1 WU per core + 1 WU would allow this to work. I set my quad core PC to run this project as my duo core laptop can't return these WUs in time. Patrick  |
||
|
|
alanb1951
Veteran Cruncher Joined: Jan 20, 2006 Post Count: 869 Status: Offline Project Badges:
|
Terribly sorry, but a day for a WU is too short. Trying to run this project is a waste of my resources. Starting a thread, and getting it bounced before it completes does nobody any good. I’ve only got a 1st gen core i7. Please extend a day to something sensible like five days. I agree! One day is way too short. I have a Core 2 Duo from 2007 and another Core 2 Duo on this project, and I've gotten it to work by adjusting my buffer to 0.01 days (and storing 0 additional days). So even if a WU takes 14 hours, I still return it in time. I wish the "1 WU per core" limit were raised so that we can participate 100% in this project instead of alternating between FAAH2 and other projects. Even 1 WU per core + 1 WU would allow this to work. I set my quad core PC to run this project as my duo core laptop can't return these WUs in time. Patrick As you've all probably noticed, there are two distinct types of task at the moment, one of which does 10,000 steps per job and the other 50,000 steps per job. The original FAH2 program did 100,000 steps but caused issues for some because of its trickle mechanism. Unless there's some way to send out the two sorts of tasks with different time limits, anything done to give the longer jobs a chance will mean the shorter jobs may tend to take longer to complete their entire process (which could take 100s of jobs if the Beta is anything to go by!) Unfortunately, that might mean we won't see a time-limit extension for these jobs... We'll just have to wait and see what happens later - I suspect that if they settle on the longer job format we'll see the time limit moved out to two days! Cheers - Al. P.S. More than 10% of the FAH2 jobs I get are retries, and well over half of those are because of "Timed Out" jobs! In fact, I've just had one where two successive tries timed out so I got the third attempt! |
||
|
|
TPCBF
Master Cruncher USA Joined: Jan 2, 2011 Post Count: 1931 Status: Offline Project Badges: 
|
That 24h deadline is a real killer, specially on slower machines (or those that run other projects, even outside of WCG)...
----------------------------------------Right now, MCM doesn't seem to send new WUs, for whatever reason, so I get boatloads of FAH2 WUs that jump ahead in the schedule, pushing everything else aside. Not good...   |
||
|
|
scannan
Cruncher The Netherlands Joined: May 1, 2007 Post Count: 6 Status: Offline Project Badges:
|
The 24h deadline is unacceptable and shows the arrogance of the project.
My machines have been doing virtually nothing but run FAH WUs at high priority, FAH is usurping all my resources and not giving other projects a chance. I am therefore in future going to process anything BUT FAH WUs. |
||
|
|
KLiK
Master Cruncher Croatia Joined: Nov 13, 2006 Post Count: 3108 Status: Offline Project Badges:
|
The 24h deadline is unacceptable and shows the arrogance of the project. My machines have been doing virtually nothing but run FAH WUs at high priority, FAH is usurping all my resources and not giving other projects a chance. I am therefore in future going to process anything BUT FAH WUs. Put app_config into your WCG project dir: <app_config> Where N is the instances (WUs) run on your computer.  |
||
|
|
NixChix
Veteran Cruncher United States Joined: Apr 29, 2007 Post Count: 1187 Status: Offline Project Badges: 
|
The 24h deadline is unacceptable and shows the arrogance of the project. My machines have been doing virtually nothing but run FAH WUs at high priority, FAH is usurping all my resources and not giving other projects a chance. I am therefore in future going to process anything BUT FAH WUs. Put app_config into your WCG project dir: <app_config> Where N is the instances (WUs) run on your computer. KLiK, Should the filename be app_config.xml? Cheers   |
||
|
|
|