We have found what prevented most of users to receive work despite having WUs in queue. Everybody should be receiving work now. There's plenty of WUS to crunch!

Ignasi,

I just received 8 (eight) wu's for 1 (one) machine with gtx480-card.

Strange????

---

Ton (ftpd) Netherlands

What's your "additional work buffer"? We had to temporarily change the scheduler algorithm.

Toni,

Normally i receive max. 2 wu's for this machine with gtx480. ID 35174

Enough info?

---

Ton (ftpd) Netherlands

Can you please cancel some of the non-running ones and see if you get one more?

Toni,

I cancelled all 8 wu's.

Downloading 6 new ones including 1 acemd2 (small wu) which is not in prerefence.

After 30 seconds again 3 new ones including 1 acemd2.

So, something is very wrong at the moment for this machine (gtx480).

I also downloaded 3 new wu's acemd2 for my gtx295 machine, which is OK. (max=4).

After some time (10 minutes) download for this machine extra 2 wu's, which is not OK now!

Enough info?

Good luck!

---

Ton (ftpd) Netherlands

For now we need everybody to get some WUs. We'll keep debugging this issue. Thanks for reporting. Please let us know if by any chance the situation fixes by itself.

Toni,

Of course i will do that!

Good luck!

---

Ton (ftpd) Netherlands

Toni,

I have one computer xp-pro 64bits with gtx260 card.
Just downloaded 6 wu's (long).

Prerefence is long wu 's and 10 days buffer (for ALL my machines).
Normally download was 2 wu's max.

Good luck!

---

Ton (ftpd) Netherlands

I'm running 2 x 260s with the preference for only long WUs but now have 12 WUs (10 long 2 ACEMD2)

Cache set for 7 days but I don't need that cache for GPUGrid tasks... is this getting set back to max 4 or do I need to tweak my end?

I have begun receiving WUs, but they are Long-Runs, and I have those disabled. I CAN NOT stand the time limits for long runs! I end up getting 14 hours into 16 and the limit is over, wasting my time and money. I don't run this 24/7 or even every day.

The server seems to ignore it for some reason.
We are trying to fix it.

gdf

Anoobis: probably you have the "allow non-preferred apps" on. Try disabling it.

Ton: does decreasing the work buffer help? The new scheduler setting may be pushing stuff in the work buffer more than the old one.

What brought this problem on in the first place? Have you been updating the BOINC server code? If so, http://boinc.berkeley.edu/trac/changeset/23360/ may be relevant.

Finally it happened!
Finally, you can download the job a few days ahead, in case the server does not allow new tasks.
Up to this point has always loaded a maximum of 2 assignments.
Please do not remove this possibility.
At the moment, I managed to get 10 jobs, which will run about 3 days.

Well, the situation seems to have swung the other way: there is no work at all for both the acemdlong and the acemd2 apps.

Well, the situation seems to have swung the other way: there is no work at all for both the acemdlong and the acemd2 apps.

This is exactly why they had the low caches and short turnarounds... they have a limited number of WUs and need the current ones to make the next batch. Because it's all sitting in people queues, there is less work for us to do.

Just let it ping the server for a few minutes and as soon as someone turns something in you should be able to grab one.

Hope they fix this soon. In the mean time, lower your cache to .75 days to keep it about where it was before. With that you should have plenty of time to get the next WU before you complete the current one yet not stock up and make other people idle. If enough people do this we'll get back to normal operation until they fix this on the server side.

I've always set it to 0.02 days. That way, it only gets new WUs when the current one is about half an hour away from finishing.

The scheduler change we attempted sent out all the WUs. We'll try to fix today.