| log in |
Message boards : Number crunching : new workunit queue size (6)
1 · 2 · 3 · 4 . . . 6 · Next
| Author | Message |
|---|---|
|
Let me know if the increase queue size helps at all with the work availability. | |
| ID: 13057 · Rating: 0 · rate:
| |
Let me know if the increase queue size helps at all with the work availability. Looking forward to it Travis, but right now I have this;
No work availabilty just now [edit] I just got a task. Whooohoooo! :) ____________ | |
| ID: 13058 · Rating: 0 · rate:
| |
Let me know if the increase queue size helps at all with the work availability. Yeah, I just restarted the server :P Work should start flowing now. ____________ | |
| ID: 13059 · Rating: 0 · rate:
| |
Let me know if the increase queue size helps at all with the work availability. Not really 27/02/2009 17:34:31 Milkyway@home Sending scheduler request: Requested by user. 27/02/2009 17:34:31 Milkyway@home Reporting 1 completed tasks, requesting new tasks 27/02/2009 17:34:36 Milkyway@home Scheduler request completed: got 0 new tasks 27/02/2009 17:35:07 Milkyway@home Sending scheduler request: Requested by user. 27/02/2009 17:35:07 Milkyway@home Requesting new tasks 27/02/2009 17:35:12 Milkyway@home Scheduler request completed: got 0 new tasks :( | |
| ID: 13060 · Rating: 0 · rate:
| |
|
Still nothing here. | |
| ID: 13061 · Rating: 0 · rate:
| |
Let me know if the increase queue size helps at all with the work availability. Yes, I just got a task, but no more;
____________ | |
| ID: 13062 · Rating: 0 · rate:
| |
|
Hmmm... | |
| ID: 13064 · Rating: 0 · rate:
| |
|
Nothing at all since that one task;
____________ | |
| ID: 13065 · Rating: 0 · rate:
| |
|
> got 49 WU's on one machine, 50 WU's on another but these are the exception... mostly '0 new tasks' after repeated manual primes... | |
| ID: 13067 · Rating: 0 · rate:
| |
|
It's gonna take the server awhile to catch up I think. Give it a little time :) | |
| ID: 13068 · Rating: 0 · rate:
| |
|
Well I haven't been following their work feeder problem that closely. However, in general BOINC terms, if you cannot transition enough work fast enough into the schedulers limited size queue, then this is what you end up seeing even if there is plenty of tasks coming out of the work generator(s). | |
| ID: 13069 · Rating: 0 · rate:
| |
|
Just got 80 for the Quad. | |
| ID: 13071 · Rating: 0 · rate:
| |
|
| |
| ID: 13072 · Rating: 0 · rate:
| |
Change can be good :) | |
| ID: 13073 · Rating: 0 · rate:
| |
|
Yup, the new limit came down right away on two machines with one manual update. Looks good so far. | |
| ID: 13074 · Rating: 0 · rate:
| |
Well I haven't been following their work feeder problem that closely. However, in general BOINC terms, if you cannot transition enough work fast enough into the schedulers limited size queue, then this is what you end up seeing even if there is plenty of tasks coming out of the work generator(s). Yeah, I'm thinking this might be the problem. Now I just have to figure out how to increase the scheduler's queue size. ____________ | |
| ID: 13075 · Rating: 0 · rate:
| |
|
I'm not seeing a reduction in the amount of '0 new tasks' and am not hitting the WU download limit. | |
| ID: 13079 · Rating: 0 · rate:
| |
|
Sitting idle here ... sigh ... when I checked the server page it said 500 available ... now 437 ... refetch master file, still nothing ... | |
| ID: 13081 · Rating: 0 · rate:
| |
|
Nearly 80 new WU here aswell. | |
| ID: 13088 · Rating: 0 · rate:
| |
|
I'm wondering if one could code a script which would request an update at say 15 second intervals automatically -- that would eventually get work, of course hammering the server might not have the right effect if such a script got out in the wild.... | |
| ID: 13089 · Rating: 0 · rate:
| |
Message boards :
Number crunching :
new workunit queue size (6)