Questions and Answers :
Windows :
20 tasks per day?
Message board moderation
Author | Message |
---|---|
Send message Joined: 2 May 11 Posts: 47 Credit: 319,540,306 RAC: 1 |
I am getting the message that I cannot get new tasks, because I am allowed only 20 tasks per day. Sup? Reno, NV Team SETI.USA |
Send message Joined: 2 May 11 Posts: 65 Credit: 242,754,987 RAC: 0 |
From which computer ID do you get this error? You can look at http://moowrap.net/hosts_user.php?userid=483 for list. Thanks |
Send message Joined: 2 May 11 Posts: 47 Credit: 319,540,306 RAC: 1 |
From which computer ID do you get this error? Well, it happens to any machine where I abort 20 tasks or more. In this case it is this one: http://moowrap.net/show_host_detail.php?hostid=118 P.S. Your spam filter is too strong. It thinks a link to this same web site is spam. I had to post without the link, and then edit the post to add the link, to work around it. Reno, NV Team SETI.USA |
Send message Joined: 6 May 11 Posts: 15 Credit: 692,725,672 RAC: 60 |
P.S. Your spam filter is too strong. It thinks a link to this same web site is spam. I had to post without the link, and then edit the post to add the link, to work around it. I'll second that motion...... |
Send message Joined: 3 May 11 Posts: 11 Credit: 994,104,261 RAC: 487,352 |
Not really a surprise if you are aborting WUs. At some projects that brings down the tasks/day limit to prevent generation of huge amounts of invalid/aborted WUs by a single host. It usually will go up again with valid WUs delivered by that host. |
Send message Joined: 2 May 11 Posts: 47 Credit: 319,540,306 RAC: 1 |
|
Send message Joined: 2 May 11 Posts: 27 Credit: 1,151,788 RAC: 0 |
It *IS* surprising to have such a low trigger. Most projects use 100 or 1000. i don't know how it is set up, but your host details still show that you killed at least 42 tasks in a row. probably a bad idea... |
Send message Joined: 2 May 11 Posts: 47 Credit: 319,540,306 RAC: 1 |
|
Send message Joined: 20 Apr 11 Posts: 388 Credit: 822,356,221 RAC: 0 |
I am getting the message that I cannot get new tasks, because I am allowed only 20 tasks per day. Sup? Every error (incl. aborted tasks) lowers the quota by 1 and at the moment we have a daily quota of 500 tasks. Quota level is reset every day and also positive quota is negated due to returning an error. Any success tasks do increase the quota level. Are you (or somebody else) still having problems with quota levels? I can made some adjustments if there's problems with this setting. -w |
Send message Joined: 2 May 11 Posts: 47 Credit: 319,540,306 RAC: 1 |
|
Send message Joined: 2 Jun 11 Posts: 1 Credit: 24,393,979 RAC: 0 |
Yeah i 'we got only 25 wu's today. And a lot of times it says there work for CPU (but im only crunching on GPU) so no tasks. While on ur site it says there are wu's to be crunched. Any idea why? |
Send message Joined: 20 Apr 11 Posts: 388 Credit: 822,356,221 RAC: 0 |
Yeah i 'we got only 25 wu's today. And a lot of times it says there work for CPU (but im only crunching on GPU) so no tasks. While on ur site it says there are wu's to be crunched. Any idea why? You have CPU crunching disabled so that's why scheduler doesn't send you any CPU units. You probably have disabled it on purpose so those messages are expected even though they can be a bit confusing. For GPU limits, it seems your BOINC Client is not requesting more work so none is sent. Maybe you have it set with so small buffer that it doesn't need more than 10. Here's some log lines from your last request: 2011-06-10 22:23:25.5606 [PID=28770] [quota] GPU: base 500 scaled 1000 njobs 10 2011-06-10 22:23:25.5606 [PID=28770] [req] ATI: req 17.47 sec, 0.00 instances; est delay 0.00 2011-06-10 22:23:25.6424 [PID=28770] [quota] [AV#12] scaled max jobs per day: 2256 2011-06-10 22:23:25.6441 [PID=28770] [HOST#1849] Sending [RESULT#714493 dnetc_r72_1307733493_12_768_0], est. dur. 3093.29 seconds, host 1079.90/3266.33 GFLOPS It does show that your host has 10 jobs in progress and it has 2256 daily limit on our end. Host requests ~18 seconds of more work which is satisfied by sending one huge workunit (scheduler thinks will take about 52 minutes to process). -w |