Status / Credit (Nov 03 2010)

...
Observation: the backlog of results 'ready to send' ran out, for both MB and AP, around 10:00 UTC, or a few minutes before. There's still a trickle, but effectively no new downloads will have been added to the download server queue since then.

The download pipe remained saturated at 93 Mbit/sec until about 10:50 UTC, the best part of an hour later. That gives us some idea of the relative speeds of the various project components: I think we need to use the remaining time before the new servers arrive to work out some way of helping the scheduler request/reply messages get through (and hence avoid creating a new set of ghosts), while Oscar and friend keep the pipe full.

The 1148513 MB and 26888 AP in "ready to send" at the start plus about 12000 MB and 5000 AP reissues created during the saturation period would have taken nearly 19 hours of download with an actual throughput of 90 Mbps. I suspect ghost creation of 100000 or more.

With the queues drained as much as possible by other means, I hope the staff will try <resend_lost_results>1</resend_lost_results> in the project config.xml at least for short periods. Bursts of activity caused by that should be tolerable, and go a long way toward having the server "in progress" actually match what is on participants' hosts. This being Friday, I expect whoever is in the lab has other plans, but maybe next week?

Joe

The one item of information that I have not seen is "When will the new servers arrive?" I understand that the PO has been placed, but there has been no mention of an arrival date or an estimated "On Line" date. Thanks,
Dave

The one item of information that I have not seen is "When will the new servers arrive?" I understand that the PO has been placed, but there has been no mention of an arrival date or an estimated "On Line" date. Thanks,
Dave

The order is out the door and we expect to have the new machines in hand in 2 weeks.

The time line we are looking at is about one month - two weeks for the servers to arrive and another two to get them going. We'll see as time goes on whether or not that's too aggressive.

In the last 2-3 weeks both my pc do not receive any workunit, and then Boinc is not working for seti. Only seti@home does not work. Why? Seti is halted?

Someone has about 1.5 million WU's looking at server, Must be very slow returning, I run out and my pc is slow

But these weeks, with capacity to burn, I guess a more parallel work-mode might come in handy. If one or two extra results were distributed already today, and returned tomorrow, then that old result that was sent out in October and times out next week will no longer need to be resent (and thus kept active), because the WU will already have the required quorum of two results and can be finalized.

Just a query - while we're waiting for the new servers, how about Beta granting credit for returned WU's? I returned 85 when Beta finally came up, and received another 40 or so from the built-up un-crunched queue - I've been steadily returning those as they've crunched, but my Beta stats line is flat since sometime in September! Or would this be too much on the substitute database server??
____________
.

Just a query - while we're waiting for the new servers, how about Beta granting credit for returned WU's? I returned 85 when Beta finally came up, and received another 40 or so from the built-up un-crunched queue - I've been steadily returning those as they've crunched, but my Beta stats line is flat since sometime in September! Or would this be too much on the substitute database server??

My Beta stats line is flat since sometime in September! Or would this be too much on the substitute database server??

My Beta stats line is flat since sometime in September! Or would this be too much on the substitute database server??

Beta validators are off at Beta there are 43,610 waiting validation as of 13 Nov 2010 4:48:08 UTC. data-driven web pages & vote_monitor are the only things running