| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: FightAIDS@Home Phase 2
Thread: Fight@home want the results to fast |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 16
|
|
| Author |
|
|
Gerhard_594982
Cruncher Joined: Apr 28, 2007 Post Count: 9 Status: Offline Project Badges: 
|
I give my time for Aids@home, which is just stupid. These leaders just want to have the results too fast and my little computers can not do that. So it is wasted time, when I have to cancel a task again, because the computer does not make it in time. Instead of 24 hours you can wait 48 or 72 hours. If you've been researching it for 40 years now, then a few days can not be decisive.
|
||
|
|
Macroman
Advanced Cruncher Joined: Jun 4, 2005 Post Count: 112 Status: Offline Project Badges: 
|
I agree 100%. Run a different project. It is your choice.
|
||
|
|
Robokapp
Senior Cruncher Joined: Feb 6, 2012 Post Count: 264 Status: Offline Project Badges: 
|
i always wondered why it's so fast...while my computers can do it just fine, there's no way it will ever comfortably fit into an android...
I'm fine accepting a good reason for it but not knowing why this is the way it is, it feels like leaving potential crunchers out for no obvious reason... I remember "back in my day" when Clean Energy Project was flagged for being intensive...maybe FAAh should also receive a more high-end flag? |
||
|
|
Falconet
Master Cruncher Portugal Joined: Mar 9, 2009 Post Count: 3315 Status: Offline Project Badges: 
|
I don't have the link, but it has been explained why it is the way it is. It has to do with something about how new workunits are generated from the previous ones or something like that. Any increase in deadline would exponentially delay the work.
----------------------------------------At least, I think it is something like that. Someone else might know it better than I.  - AMD Ryzen 5 1600AF 6C/12T 3.2 GHz - 85W - AMD Ryzen 5 2500U 4C/8T 2.0 GHz - 28W - AMD Ryzen 7 7730U 8C/16T 3.0 GHz |
||
|
|
ErikaT
Former World Community Grid Admin USA Joined: Apr 27, 2009 Post Count: 912 Status: Offline Project Badges:
|
Hello,
Information on FightAIDS@Home - Phase 2 work units can be found here, which includes details of why the work units have short deadlines. Thank you for your support, ErikaT |
||
|
|
Falconet
Master Cruncher Portugal Joined: Mar 9, 2009 Post Count: 3315 Status: Offline Project Badges:
|
Thank you ErikaT.
----------------------------------------- AMD Ryzen 5 1600AF 6C/12T 3.2 GHz - 85W - AMD Ryzen 5 2500U 4C/8T 2.0 GHz - 28W - AMD Ryzen 7 7730U 8C/16T 3.0 GHz |
||
|
|
Bearcat
Master Cruncher USA Joined: Jan 6, 2007 Post Count: 2803 Status: Offline Project Badges: 
|
So what happens when we are a few hours late from deadline? Just saw one of mine was sent to another computer right at deadline. Do I abort the ones not going to make deadline so I don't wast computer time?
----------------------------------------
Crunching for humanity since 2007!
 |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Just finish the job. If your computer has not started the job yet, which is doubtful considering tasks with 24 hour deadline are run with priority, then the server sends an abort to your client.
|
||
|
|
alanb1951
Veteran Cruncher Joined: Jan 20, 2006 Post Count: 1317 Status: Offline Project Badges:
|
Bearcat wrote:
----------------------------------------So what happens when we are a few hours late from deadline? Just saw one of mine was sent to another computer right at deadline. Do I abort the ones not going to make deadline so I don't wast computer time? lavaflow replied: Just finish the job. If your computer has not started the job yet, which is doubtful considering tasks with 24 hour deadline are run with priority, then the server sends an abort to your client. I'd just like to observe that I'm often on the receiving end of server aborts on FAH2, HST1, MCM1 and MIP1 tasks because I've been sent a retry and the late reply comes in before I've started to run the retry; this isn't a serious issue for tasks that don't need to download much data, but it might irritate me if that ever happens with ARP1! In an ideal world folks would tweak their workloads to minimise the likelihood of over-running task time limits. However, there will always be users who are unaware of the issue or either can't or won't do anything about it, so there will always be "Too Late" tasks that turn into "Valid" tasks with possible aborts for retry jobs. So, as lavaflow says, just finish the job! Cheers - Al. P.S. Out of interest, nearly 10% of all FAH2 jobs I've had for the current set of experiments have been retries, and about 45% of those retries have been because the original task hasn't replied within 24 hours. Admittedly, it's only a sample of just under 7000 tasks, but... [Edit to the can't/won't phraseology] [Edit 1 times, last edit by alanb1951 at Nov 3, 2019 4:14:59 AM] |
||
|
|
Bearcat
Master Cruncher USA Joined: Jan 6, 2007 Post Count: 2803 Status: Offline Project Badges:
|
I fixed the overload/late returns. Just limited the amount of wu's to the number of threads available. Return dates are out with time to spare. Fills right up as one is completed.
----------------------------------------
Crunching for humanity since 2007!
|
||
|
|
|