........ it was good whilst it lasted - managed to 'fill-up' on WUs .... but the last 2 are now showing estimates of 297hrs.... DCF has gone back up to 28.xxxxxx.
At what point is the DCF set in the client and by what?

I've got an empty cache and still cannot get any WU. Does anybody else have this problem?

13/12/2008 11:29:09|GPUGRID|Message from server: No work sent
13/12/2008 11:29:09|GPUGRID|Message from server: Full-atom molecular dynamics on Cell processor is not available for your type of computer.
13/12/2008 11:29:09|GPUGRID|Message from server: Full-atom molecular dynamics for Cell processor is not available for your type of computer.

I have ample std and ltd to be able to keep a 4 task cache on a quad but until they fix the BOINC client and/or the task est time my boxes will run out of work unless constantly babysat which can't happen....the 24hour back-off time increases the chances of idle time :(

that 24 hour backoff is (beneath DCF) the biggest problem right now.

brilliant idea to put every host not beeing babysitted asleep.. :(

The same problem here. Without manually updating my PCs are very fast without work. I'm really enthusiastic at the start of the project and purchased 6 big graphic cards, but at the moment I'm really frustrated. Since the version 6.3.19 I can't see any enhancement. It's much more important to feed the 8800GT up to GTX260²/GTX280 with enough work then satisfy the user with the 8500GT. Better 3 WUs in reserve than no WU for a half day on this fast cards.

---

I am trying to contact Anderson to see how to fix this.

GDF

........ Thanks GDF.

I see the number of WUs in progress is dropping steadily - at least I think it is, unless the past few days have been uncharacteristically high. Which I guess is hosts running dry.

On a plus note - my son's PS3 happily bumbles along without need of intervention (until he wants to use it!).

At some future stage could we see a differentiation on the Server Status page between PS3 and GPU work?

Yes, we will differentiate server status.

I have reverted the server code to two days ago to see if things improves.
But still the workunits are requesting more flops than before.

GDF.

It's a strange one.
Can you do anything about the 24 hour back off that accompanies the messages?

Probably not.

gdf

I have reverted the workunits to values just a bit higher than before the changes.
Hopefully, we will be able to normalize to the correct ones slowly during the next weeks. In one go, it does nor work.

Let's see if we are back to normal now.
gdf

Still getting the following message. It then backs off for 24 hrs and my comp goes idle. Lucky for me wu's take a day of crunching, but I'm still idle for 4hrs. DCF has been manually set to 1.0.

14/12/2008 6:03:14 AM|GPUGRID|Sending scheduler request: To fetch work. Requesting 112428 seconds of work, reporting 0 completed tasks
14/12/2008 6:03:19 AM|GPUGRID|Scheduler request completed: got 0 new tasks
14/12/2008 6:03:19 AM|GPUGRID|Message from server: No work sent
14/12/2008 6:03:19 AM|GPUGRID|Message from server: Full-atom molecular dynamics for Cell processor is not available for your type of computer.
14/12/2008 6:03:19 AM|GPUGRID|Message from server: Full-atom molecular dynamics on Cell processor is not available for your type of computer.
14/12/2008 6:03:19 AM|GPUGRID|Message from server: (won't finish in time) BOINC runs 99.9% of time, computation enabled 100.0% of that

How much is the estimated time when your wu start?
I have checked on the server and your dcf is close to 1, so it should be fine.

GDF

Estimated wu time was only 4hrs with a dcf of 1. Things appear to have come good now. I have 4 wu's in the cache.

I'm now seeing wu's that only claim 2435 credits vs 3232.

nothing good now - just got a fresh WU - estimated runtime for a 260: 1901 hours.

this is going to be a reasonable attempt for gaining that fubar@home badge. :(

reset project please.

gdf