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

---

. . . Accolades to Berkeley . . . and To Each of You [Thanks for the Post Matt]

---

BOINC Wiki . . .

Science Status Page . . .

There's always a bright side during work tranmission 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.
- Matt

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'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.

---

.

Hello, from Albany, CA!...

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?

Sometimes we do this, but usually if the queues are large enough to be deemed a "problem" then it usually take days to drain during "low usage" times like this weekend (sometime days even during "no usage" times - the assimilator can only work so fast).

- 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

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

I think that all workunits are deemed available for either CUDA or regular CPU, but any given instance of the CUDA client can only claim up to N workunits per day. I'm not sure what N is offhand...

- 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

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

---

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

The reason I asked is that I have NO CUDA capable GPU's to date, and I'm getting the occasional "no work available for your CPU" flag, (as mentioned in my first post...)

---

.

Hello, from Albany, CA!...

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.

As I understand there is no such thing as a "CUDA" work unit from a server perspective. In the server they are all MB WU's (i.e. 6.03's) and it is given the "6.08" designation only when it is delivered to a CUDA client. That's why most CUDA WU's currently validate again CPU-crunched tasks.

F.

---

>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?

Hehe, maybe it encourages you to move to CUDA too ? ;) ;)

>Hehe, maybe it encourages you to move to CUDA too ?<

Sure, I'll move to CUDA today if you buy the hardware. Only been 2 years since I've had a job. That's why I play poker. ;-)

>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...)

---

.

Hello, from Albany, CA!...

>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...)

Unless there are 3 or more tasks in the validation, in which case the high and low are both dropped and the rest are averaged.

---

BOINC WIKI

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

If you check out thread AK V8 + CUDA MB team work mod you can find out how to do it.

You mean like this one? http://setiathome.berkeley.edu/result.php?resultid=1166518822

With the opt-App Randy C pointed out I have one running on my GPU and two running on the CPUs. They all show up as 6.08s

---

PROUD MEMBER OF Team Starfire World BOINC

No work units on the UltraSparc-10 since last weekend. It keeps saying "requesting work".. but none arrives.

Any available?

Mark