was it "sends" or is it "sent"? Does it still do after implementation of the "New projects, auto opt-in"? If so, please document .

Appears to be happening again, have a couple of Faah jobs, quorum of one pending for three hours.
A server status site is only useful to a point,It only shows the darn things are turned on not that they are actually working which can mask a problem as I have found on cpdn many a time
What is needed is louder bells and whistles

Yup agreed most definitely the more info the better..
Somethings working as all my jobs just validated
Chris.

The server status page is interesting to look at but I'm not sure it would provide as much use as folks think it would.

There are many times throughout the day that we suspend the validators/assimilators/transitioners/file_deletor/db_purge via scripts in order to reduce contention on the database while other processes are executing certain tasks. They are probably off 15% of the day or so.

As far as monitoring the status goes, we have scripts in place that will send text messages to several staff members cell phones, work and personal email addresses alerting them when BOINC processes have stopped running. We also have the same thing for a lot of the standard system monitoring (filesystems, is apache running, etc).

This past weekends issue was unusual becuase one of the backend servers completely froze up. Depending how the server status page was implemented, then the page might have continued to report that the processes were running (the default status page provided with BOINC would have shown this).

As far as displaying various queues go, those queries are extra load on the BOINC database which is severely taxed right now. In our new environment they might be tolerable.

All of this is not to say that we won't do this someday, but we are going to be focusing on things such as updating the forum software before we work on this. I am very much hoping that we can get the kinks worked out of the new environment quickly and settle into a nice period next year of focusing on improvements rather than the more mundane but absolutely essential work of upgrading hardware and underlying software.

I understand all of this, and I agree that it is a low priority compared to actually getting this thing to run smoothly. I, for one, don't care about the "Server Status" so much as the "Ready to Send" component.

I have the option to get any work available set for WCG and so never have a problem with workload. However, I grab the RTS information from other projects that I run as part of a calculation used to assign a priority designation to each. I then use the designation result to rotate runtimes for them under the BOINC client. Not having the RTS information for WCG skews my results. I have been able to make adjustments, but...

There are multiple projects being run under WCG, but if only indicating RTS, a way to do it would be the way CPDN does it. While CPDN also shows the SS information, they do break up the different projects under the RTS showing how much work is available to each.

If it is possible to show only the RTS information, it would provide an indication of how close to completion any project is or if new work has been added. It might help those that like to opt-in to certain projects by indicating to them that it may be time to pick another.

If the information could be incorporated into the main stats page, it would eliminate the need for a new page, but may add to webpage generation times depending on whether the information is live or sampled during a stats update. Heck, it could be made accessible via XML or RSS and kept off the website entirely and then would also be subject to live queries or sampled updates.

Well, thanks for your time. I hope these suggestions are considered when your priority list gets to the status page. In the meantime, thanks for keeping this place going as well as you have.