Forum > Discussion Forum
When corrupted results get validated...
Claggy:
--- Quote from: perryjay on 23 Aug 2010, 04:09:18 pm ---That smithwr has 18,000 tasks on his list. It's scary thinking how many of those are returning -9.
--- End quote ---
Quota system doesn't work very well does it?
Every invalid task/error resets his quota to 100, but with Seti's *8 Multiplier, he still gets 800 tasks a day,
I think the quota should go a lot lower than 100, or take the Multiplier away.
Claggy
Raistmer:
If all his results are invalid his quota should go to 1 eventually, i.e. 8 GPU tasks per day.
[BTW, it looks like very same case new quota system should protect from.
Even if he return good CPU results - GPU should be inhibited.
If not - current quota system still flawed.
]
[And GPU multiplier should be removed indeed. If GPU works fine it will have no effective limits w/o any multiplier, but if it broken this multiplier just multiplies trashed tasks... ]
perryjay:
Here's his invalid list.. http://setiathome.berkeley.edu/results.php?hostid=5293938&offset=0&show_names=0&state=4 Anyone want to try to count them? I got four pages into it and decided not! :-(
Miep:
--- Quote from: perryjay on 23 Aug 2010, 06:54:59 pm ---Here's his invalid list.. http://setiathome.berkeley.edu/results.php?hostid=5293938&offset=0&show_names=0&state=4 Anyone want to try to count them? I got four pages into it and decided not! :-(
--- End quote ---
1223 atm. put something big in offset, then work your way up or down by say 100 - or larger depinding on expectations. If you go too high it'll tell no tasks to display.
Handy to move to the oldest pending/in progress task too.
Josef W. Segur:
The smithwr3 host 5293938 several minutes ago had 147 "valid" tasks, not all of those are false overflows, as v12 apparently does not do that on VHAR or VLAR tasks and the host is also doing CPU work. It also has 1224 invalid tasks which probably are all false overflows, though I certainly didn't check more than a tiny sample.
The BOINC quota mechanism is, and always has been, only capable of protecting against totally bad processing, and even so the protection is delayed; a host which goes bad with thousands of tasks already cached is penalized too late to save those tasks.
Is there a chance the "Notices" in 6.11+ might be considered obvious enough that the servers could send a Notice that the host appears to have failed along with a command which causes BOINC to not start any more tasks for the project until the user has read the Notice and believes the problem fixed? I don't know if the BOINC devs would consider something like that, discussions about quota and related things on the boinc_dev list seem to always end inconclusively.
Joe
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version