| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: FightAIDS@Home Phase 2
Thread: 24 Hour Deadline too Short |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 112
|
|
| Author |
|
|
BladeD
Ace Cruncher USA Joined: Nov 17, 2004 Post Count: 28976 Status: Offline Project Badges: 
|
I just devote a separate Windows machine to FAH2 (only), and run all the others on Linux machines. It works. I just limit it by the number of WUs (ie. 2 at a time). |
||
|
|
Jim1348
Veteran Cruncher USA Joined: Jul 13, 2009 Post Count: 1066 Status: Offline Project Badges: 
|
I just limit it by the number of WUs (ie. 2 at a time). Yes, good use of that. I limit the MIPs to two at a time for performance reasons, though on different machines than FAH2. You could of course do both. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I just limit it by the number of WUs (ie. 2 at a time). This is what I've ended up doing as well. With storm season in full swing I make sure my workhorse machines have a queue depth of at least a day so that they have enough work to outlast any connectivity or server outages. So... now... each machine only gets 1 WU from this project per day.... and it may or may not end up being returned late. |
||
|
|
mikey159c
Cruncher Joined: Aug 21, 2008 Post Count: 11 Status: Offline Project Badges: 
|
I just give the whole pc to FAH2 tasks and let it crunch, in some cases that's 15 cpu's per pc, another shares with TB wu's and uses 23 cores to crunch. It also means when a pc crashes, like yesterday, I either swap the harddrive to an identical machine or lose wu's.
|
||
|
|
Mantakno
Cruncher Joined: Jun 9, 2008 Post Count: 45 Status: Offline Project Badges:
|
it is funny, short time, and yet client did a cpu calc what it can do so why not give client packet to match the deadline better 24hour deadline then packet should not be longer then 1hour. mine is 6hours atm, this simple stress people out with i need it now. maybe all should do as i just did turn off packet delivery and give them the finger. this was said in the most respect tone for what it try to do. but project leader fail to see what they actual did. this project should be kicked out for not have a longer timeslot, if it is that importen when raise emergency then on the project.
----------------------------------------as i understand it that actual possible in the WCG client [Edit 1 times, last edit by Mantakno at Jun 19, 2019 10:28:18 AM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
There used to be a technical warning on the device profiles for I think CEP2.
Microbiome Immunity Project OpenZika Help Stop TB FightAIDS@Home - Phase 2 (Warning: This project requires 24 hour processing return!) Mapping Cancer Markers Techs, why don't you add one for FAHB? We know the reason why, just make people aware up front! many thanks |
||
|
|
katoda
Senior Cruncher Poland Joined: Apr 28, 2007 Post Count: 172 Status: Offline Project Badges: 
|
24h deadline too short? Then what you would describe deadline of less than 9h? Because I just got this:
----------------------------------------https://www.worldcommunitygrid.org/ms/device/....do?workunitId=1168171617 Result name: FAH2_ 002387_ zinc12164843_ 000003_ 000051_ 085_ 0-- Sent time: 6/20/19 06:43:31 Time due: 6/20/19 15:07:30 I'll make it, no problem, but nevertheless something is a bit borked, I would say.  |
||
|
|
Speedy51
Veteran Cruncher New Zealand Joined: Nov 4, 2005 Post Count: 1326 Status: Offline Project Badges:
|
24h deadline too short? Then what you would describe deadline of less than 9h? Because I just got this: https://www.worldcommunitygrid.org/ms/device/....do?workunitId=1168171617 Result name: FAH2_ 002387_ zinc12164843_ 000003_ 000051_ 085_ 0-- Sent time: 6/20/19 06:43:31 Time due: 6/20/19 15:07:30 I'll make it, no problem, but nevertheless something is a bit borked, I would say. Out of curiosity how long did the task run for & are you a Linux or Windows user  |
||
|
|
katoda
Senior Cruncher Poland Joined: Apr 28, 2007 Post Count: 172 Status: Offline Project Badges:
|
This task landed on my Linux machine. Regarding the run time, unfortunately it already disappeared from my workunit list, but AFAIK it was nothing special, something between 2 to 3 hours, like most of FAAH2 workunits on this machine.
---------------------------------------- |
||
|
|
Speedy51
Veteran Cruncher New Zealand Joined: Nov 4, 2005 Post Count: 1326 Status: Offline Project Badges:
|
This task landed on my Linux machine. Regarding the run time, unfortunately it already disappeared from my workunit list, but AFAIK it was nothing special, something between 2 to 3 hours, like most of FAAH2 workunits on this machine. Thanks for the information. I haven't struck in the tasks with a short deadline. On Windows mine machine runs them and around 5.36 hours at the longest nothing under 5 hours though Windows 10 |
||
|
|
|