Darwin (Feb 17 2009)

Over the long (President's Day) weekend one of our storage servers had a headache. Not a big deal, and we got to the bottom of it today (pretty much just a RAID drive failure). We were able to get a workaround in place so we could start generating/saving workunits again, and will slowly transition back to normal over the next day or two. It has been a bit rocky the last few days because the workaround involves a different RAID with far less I/O throughput.

There's always a bright side during work transmission failures: we get to catch up on backlogged queues. So by the time we had our usual database compression/backup outage today the result table was relatively small, and therefore got packed down nice and tight. That's always helpful.

Spent most of the day with the fallout of the above, while also getting a couple systems configured for new duty - mostly administrative/CPU servers that will replace a some older clunkers.

- Matt
____________
-- BOINC/SETI@home network/web/science/development person
-- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude

Thanks, Matt....looking forward to NTPCKER going live
____________

Query - what percentage of MB units are designated as "CUDA" units, and what percentage are available to plain old cpu apps?

I'm often (even when the servers are working properly...) getting the "no work available for your cpu" flag when requesting new work. Please remember that a lot of us are either working with non-CUDA capable clients, (pre 6.4...) or have ATI graphics boards (or older Nvidia boards...) which are non-CUDA capable. I've occasionally had cpu cores (I have 10 working...) go "cold" on SETI (all computers have more than one project attached, of course, so they aren't actually "cold"!...) due to the above flag.
____________
.

Would it make any sense to turn off accepting new work a few hours before you shutdown the system on Tuesdays to get this benefit? Maybe you already do that?

Query - what percentage of MB units are designated as "CUDA" units, and what percentage are available to plain old cpu apps?

I have NEVER experienced a 6.08 CUDA work unit execute in the CPU, even when I ran out of other SETI work. I would be interested to hear if anyone has had a 6.08 CUDA work unit run in their CPU.
Rick

Query - what percentage of MB units are designated as "CUDA" units, and what percentage are available to plain old cpu apps?

I'm often (even when the servers are working properly...) getting the "no work available for your cpu" flag when requesting new work. Please remember that a lot of us are either working with non-CUDA capable clients, (pre 6.4...) or have ATI graphics boards (or older Nvidia boards...) which are non-CUDA capable. I've occasionally had cpu cores (I have 10 working...) go "cold" on SETI (all computers have more than one project attached, of course, so they aren't actually "cold"!...) due to the above flag.

>That's why most CUDA WU's currently validate again CPU-crunched tasks.<

Just wondering... is this why my CUDA capable wingman's credit of 59.71 got knocked down to my non-CUDA credit of 43.71?

>That's why most CUDA WU's currently validate again CPU-crunched tasks.<

Just wondering... is this why my CUDA capable wingman's credit of 59.71 got knocked down to my non-CUDA credit of 43.71?

>That's why most CUDA WU's currently validate again CPU-crunched tasks.<

Just wondering... is this why my CUDA capable wingman's credit of 59.71 got knocked down to my non-CUDA credit of 43.71?

Credit is always granted at the lower level to prevent overclaiming credit fraud (don't laugh - it's happened...)