Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
![]() |
World Community Grid Forums
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
No member browsing this thread |
Thread Status: Active Total posts in this thread: 1130
|
![]() |
Author |
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Maybe uplinger wishes to update the sticky post at top of this forum that answer part of your question. Update, because the A-Type will run 1/5th of the time than before with only 10 of 50 loops. The C type I think will then take over a part of that i.e. will run longer than originally set out on project launch. As for the resources, refer to the System Requirements help page and the Matrix FAQ for actual observed resources. It's needs also updating due to new sizing. Sek, I will be looking into this when I get some better numbers from the type C work units. So at the moment, type A on the chart will show 50 hours when in fact it should show closer to 10-15 hours. Thanks, -Uplinger |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
[Edit]ok, different request, for a pointer to the most succinct description of the quota algorithm. From what I'm seeing I'm guessing an accidental abort of some tasks from another project (or rather, a deliberate abort after accidentally selecting a project I didn't want to crunch) has made this host non grata for all projects none of which will give it work. It's going to run out of work before too long, is it going to be forgiven in 24 hours?
----------------------------------------[Edit 1 times, last edit by Former Member at Jul 28, 2010 1:59:00 AM] |
||
|
RT
Master Cruncher USA - Texas - DFW Joined: Dec 22, 2004 Post Count: 2636 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
[Edit]ok, different request, for a pointer to the most succinct description of the quota algorithm. From what I'm seeing I'm guessing an accidental abort of some tasks from another project (or rather, a deliberate abort after accidentally selecting a project I didn't want to crunch) has made this host non grata for all projects none of which will give it work. It's going to run out of work before too long, is it going to be forgiven in 24 hours? I know some folks (like me ![]() ---------------------------------------- [Edit 1 times, last edit by RT at Jul 28, 2010 3:17:56 AM] |
||
|
pirogue
Veteran Cruncher USA Joined: Dec 8, 2008 Post Count: 685 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
[Edit]ok, different request, for a pointer to the most succinct description of the quota algorithm. From what I'm seeing I'm guessing an accidental abort of some tasks from another project (or rather, a deliberate abort after accidentally selecting a project I didn't want to crunch) has made this host non grata for all projects none of which will give it work. It's going to run out of work before too long, is it going to be forgiven in 24 hours? It will be forgiven. I can't remember if it happens at 12:00 GMT or 00:00 GMT, but it does happen. At that point it will get new WUs and start building back up its reliability rating. |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I thought from reading another project's forum that the quota/reliability stats were kept per WCG project, not across projects. It was a complaint about that actually, though I'd wish for it to be true at this moment!
|
||
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
hmmm, succinct, hmmm, maybe if you translate the verbose from this FAQ: http://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,28636
----------------------------------------If you have work still to crunch through and it turns valid AND you have not used up the 80 WU max per device core per day for a previously reliable client then you could get more today. If not, then there has to have been a bunch of 'accidentals' going on. If then, send a deep grovel mail to the support contact [to include a full technical explanation] and maybe they'll reset the quota for you... Else, the wait is on till 00:00:01 UTC to get 1 to proof worthy. 80 is allot which is 320 for a quad, my 64 bit linux managing to do about 65-70 HCC jobs in a day i.e. never ever getting close to the core quota. Someone who wishes to build a 10 day HCC cache will need initially several days to get there. With a sample of 70 *10 / (4*80) = 2.2 day, but since 65-70 will have been completed on the first and second day, it's only on the 3rd day that full stock can be had. 10 days is though not recommended for various issues, mostly because just the smallest downtime will cause the last tasks to go overdue and get auto-cancelled by the newer clients which goes against the daily quota.
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
PS, the quota is across all sciences, else someone can do big damage to the supply chain with a dual socket hexcore HT.
----------------------------------------
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
PS, the quota is across all sciences, else someone can do big damage to the supply chain with a dual socket hexcore HT. That makes the most sense, just commenting on what I read elsewhere. Thanks for the pointer to your earlier post, it's clear enough. Of course I made my mistake right after UTC midnight, but finally have returned enough work to get a small trickle, enough to get the host through the night. Certainly want to have some quota left when more DDDT-2 work arrives! Though this host probably won't go back into the reliable category any time soon. I'm sure others have also wished for the relevant host stats to be visible on the site and this isn't the place for the topic, but thanks for answering my question anyway. ![]() [Edit 2 times, last edit by Former Member at Jul 28, 2010 7:12:52 AM] |
||
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
<sot>Was discussing this with knreed some time ago and how to plant a festive message in the client log whenever a host moves in or out of the R++ reliability class, and double works as a pre-alert that something is going awry or had a bad condition. He then joked to insert "Congratulations, your client is now deemed reliable". There's a table somewhere in the FAQ's that shows the 'spiel' for hosts that have reached maximum rating which is 0.1%. Once there a device needs to produce 12 consecutive errors before exceeded the 0.2% minimum to qualify for high priority jobs such as DDDT-2 A Type which goes on top to consistently returning results within 2 days. That will probably stay because there has to be a higher confidence that the bulk of the A Type work comes back quickly for the B/C generation... but we continue to run these benchmark/reference ts tasks... we've not really in earnest started of the real production jobs</sot>
----------------------------------------
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
RT
Master Cruncher USA - Texas - DFW Joined: Dec 22, 2004 Post Count: 2636 Status: Offline Project Badges: ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
<sot>Was discussing this with knreed some time ago and how to plant a festive message in the client log whenever a host moves in or out of the R++ reliability class, and double works as a pre-alert that something is going awry or had a bad condition. He then joked to insert "Congratulations, your client is now deemed reliable". There's a table somewhere in the FAQ's that shows the 'spiel' for hosts that have reached maximum rating which is 0.1%. Once there a device needs to produce 12 consecutive errors before exceeded the 0.2% minimum to qualify for high priority jobs such as DDDT-2 A Type which goes on top to consistently returning results within 2 days. That will probably stay because there has to be a higher confidence that the bulk of the A Type work comes back quickly for the B/C generation... but we continue to run these benchmark/reference ts tasks... we've not really in earnest started of the real production jobs</sot> Thanks Much for the info. I was trying to manage my queues to get some more DDDT2s and fubared it. So now 3 or 4 of my super reliable machines will not be so rated for a bit. Mayhaps that is why I did not get any DDDT2s last evening even though my trap was set(for the first time). ![]() ---------------------------------------- [Edit 1 times, last edit by RT at Jul 28, 2010 12:43:52 PM] |
||
|
|
![]() |