Questions on Servers and WU's |
![]() |
| log in |
Message boards : Number crunching : Questions on Servers and WU's
| Author | Message |
|---|---|
|
According to the Server status page as at 0200 UTC there is 1.4 million MB and nearly 5k AP WU's available for download. The Cricket graphs show the system is nowhere near max'ed out and the Server status page has a "green board". | |
| ID: 913154 · | |
|
I am seeing similar behaviour 1.4 million MB and nearly 5.7k AP WU's available for download. | |
| ID: 913160 · | |
Q1)Why then do I keep getting "No jobs available" messages on my boxes ? Where and what is the problem ? The count is the total number of work units split, but not yet assigned. The splitters split the work. The feeder grabs 100 work units and those are available to the scheduler. If the feeder queue is empty (if the scheduler has assigned all of the 100 work unit batch) it will report "no work available" -- until the feeder grabs another 100 work units. Among other things, this keeps the download server from getting 100,000 requests to download all at once. ____________ | |
| ID: 913162 · | |
There is a thread at lunatics, about rebranding 6.03(CPU) into 6.08(GPU)WUs and vice versa. GPU rebranding There are couple solutions, but I'm using ReSchedule 1.7 cause it's standalone and easy to use. ____________ Who the hell is General Failure and why is he reading my harddisk?¿ | |
| ID: 913171 · | |
According to the Server status page as at 0200 UTC there is 1.4 million MB and nearly 5k AP WU's available for download. The Cricket graphs show the system is nowhere near max'ed out and the Server status page has a "green board". See Matt's post from last December for that issue. Just what is delaying the Feeder is a very good question, though. Joe | |
| ID: 913187 · | |
|
All OK now with the rebranding. Thanks Zeus for the pointer to the rebranding program and to Ned and Joe (again) for the answers to the server question. | |
| ID: 913195 · | |
|
That ReSchedule 1.7 looks like a nice little toy. I think I'm going to enjoy playing with that one :-) Thanks again Zeus and to the boys from Lunatics | |
| ID: 913235 · | |
See Matt's post from last December for that issue. Just what is delaying the Feeder is a very good question, though. Something is slowing down the scheduler too. It doesn't usually take 86 seconds to get a null reponse: 02/07/2009 15:20:10|SETI@home|Sending scheduler request: To fetch work 02/07/2009 15:20:10|SETI@home|Requesting 368777 seconds of new work 02/07/2009 15:21:36|SETI@home|Scheduler RPC succeeded [server version 607] 02/07/2009 15:21:36|SETI@home|Message from server: (Project has no jobs available) | |
| ID: 913276 · | |
See Matt's post from last December for that issue. Just what is delaying the Feeder is a very good question, though. ... all the other traffic would do this. It could take 86 seconds just to get the SYN/SYN+ACK/ACK through a heavily loaded wire successfully. At times, the BOINC client is quite effectively doing a Distributed Denial of Service attack on the BOINC servers. ____________ | |
| ID: 913352 · | |
Message boards : Number crunching : Questions on Servers and WU's
| Copyright © 2013 University of California |