| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Active Research
Forum: Africa Rainfall Project
Thread: Work Available |
| Member(s) browsing this thread: TonyEllis |
|
Thread Status: Active Total posts in this thread: 3261
|
|
| Author |
|
|
Jim1348
Veteran Cruncher USA Joined: Jul 13, 2009 Post Count: 1066 Status: Offline Project Badges: 
|
They probably should just limit them to two per machine, maximum. That would not cost them anything in throughput, since most machines/internet connections can't handle more anyway. And they would eliminate the delays (and worse, timeouts), which just limit the number of new work they can generate.
----------------------------------------They need to get tough. If people are not whining, it is not being done right. EDIT: Possibly a better way is to shorten the timeouts. Then, you could download more if you have a fast machine, but they would disappear in a puff of smoke if you do not get to them in time. [Edit 1 times, last edit by Jim1348 at Nov 2, 2019 3:20:55 PM] |
||
|
|
gb009761
Master Cruncher Scotland Joined: Apr 6, 2005 Post Count: 2982 Status: Offline Project Badges: 
|
Jim1348, another option would be to do similar to the Beta WU's on the initial project start-up, as then that'd prevent crunchers from hogging WU's and allow a wider range of machines to provide a wider range of processors/combinations.
----------------------------------------Obviously, once the techs are happy with the project launch and everything is looking good/the speed of WU generation has reached 'peak performance', then the handbrake can be fully released.  |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: 
|
Jim1348, another option would be to do similar to the Beta WU's on the initial project start-up, as then that'd prevent crunchers from hogging WU's and allow a wider range of machines to provide a wider range of processors/combinations. Obviously, once the techs are happy with the project launch and everything is looking good/the speed of WU generation has reached 'peak performance', then the handbrake can be fully released. Why should people who have a large amount of cores available be penalized for getting more WUs? They’re paying the freight on costs. With the limited amount of work going out it’s not “hogging” if they get more.
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
----------------------------------------  [Edit 1 times, last edit by nanoprobe at Nov 2, 2019 4:06:29 PM] |
||
|
|
gb009761
Master Cruncher Scotland Joined: Apr 6, 2005 Post Count: 2982 Status: Offline Project Badges:
|
Jim1348, another option would be to do similar to the Beta WU's on the initial project start-up, as then that'd prevent crunchers from hogging WU's and allow a wider range of machines to provide a wider range of processors/combinations. Obviously, once the techs are happy with the project launch and everything is looking good/the speed of WU generation has reached 'peak performance', then the handbrake can be fully released. Why should people who have a large amount of cores available be penalized for getting more WUs? They’re paying the freight on costs. With the limited amount of work going out it’s not “hogging” if they get more. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Currently there are less than 1000 wu being processed per day so it seems there isn't all that much data to crunch at least for now. Compare that to over 500,000 per day in MIP. Maybe in time the pace will increase.
https://www.worldcommunitygrid.org/stat/viewP...&numRecordsPerPage=14 |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges:
|
Jim1348, another option would be to do similar to the Beta WU's on the initial project start-up, as then that'd prevent crunchers from hogging WU's and allow a wider range of machines to provide a wider range of processors/combinations. Obviously, once the techs are happy with the project launch and everything is looking good/the speed of WU generation has reached 'peak performance', then the handbrake can be fully released. Why should people who have a large amount of cores available be penalized for getting more WUs? They’re paying the freight on costs. With the limited amount of work going out it’s not “hogging” if they get more. I highly doubt people with 250 cores are going to get 250 WUs at any 1 time. I have not received anywhere near 1 WU per core so your hogging statement kind of contradicts itself. Who’s hogging?
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
|
||
|
|
Jack007
Master Cruncher CANADA Joined: Feb 25, 2005 Post Count: 1604 Status: Offline Project Badges: 
|
I would be happy to have 2 at a time, if I could keep getting 2 all the time.
----------------------------------------EDIT: Well what do you know, Ask and ye shall receive. Picked up 2 more work units. EDIT2: Just for good measure they threw in an HSTB as well.  [Edit 2 times, last edit by Jack007 at Nov 3, 2019 2:50:33 AM] |
||
|
|
littlepeaks
Veteran Cruncher USA Joined: Apr 28, 2007 Post Count: 748 Status: Offline Project Badges:
|
10/31/2019 12:21:06 PM | World Community Grid | No tasks are available for Africa Rainfall Project
<cut> 11/2/2019 1:00:08 PM | World Community Grid | No tasks are available for Africa Rainfall Project Nada so far  |
||
|
|
DrMason
Senior Cruncher Joined: Mar 16, 2007 Post Count: 153 Status: Offline Project Badges:
|
I tend to agree that the major reason isn't people hogging (that is, caching multiple days of work to crunch), but rather the general limitation on the supply of work. It remains to be seen whether it just takes a little bit to ramp the work up, or if this is going to be a work limited project like HSTB...
----------------------------------------For now, what's worked for me is to keep caches low, request for new work frequently, and reduce the max number of FAAH2 work units in device manager. The FAAH2 units have a 24 hr deadline, so I've seen them take priority over other projects (which could prevent ARP units you have from crunching, and in a worst case scenario that I've seen, create a loop where it only crunches FAAH2 until other units are 24 hours away from their deadlines). That said, even though I have a bunch of free cores and request new work about every 2-3 minutes, I'm only getting something like 13 new units a day. So your mileage may vary. Good luck to everyone!  |
||
|
|
Aurum
Master Cruncher The Great Basin Joined: Dec 24, 2017 Post Count: 2386 Status: Offline Project Badges: 
|
I have ~1,000 cores and currently have 90 ARP1 WUs Pending Validation, 120 running, and 165 Valid. If I see an ARP1 waiting to run I suspend MCM until it starts. I can see no way possible someone can hog them. I think it's time to open the floodgates. The most I've seen is about 1 ARP1 for every 5 CPU cores. Some computers get 12 and some none. But none of my computers has even come close to 1 WU per core.
----------------------------------------If someone sets their queue for 10/10 days and WCG gives them that many WUs then they've screwed up. Even at full speed no one should ever get more than 2 WUs per core regardless of their settings. Since this is a serial simulation they need completed WUs returned in 24-48 hours. Setting the deadline for a week is a big mistake. Ouch!!! Just tripped my main breaker and with so few checkpoints I just lost 10 days work, money down the drain. We need more checkpoints!!!   ...KRI please cancel all shadow-banning |
||
|
|
|