ATI isn't even a selection in the preferences anymore. How does that get missed?

It was gone for maybe 2 hours. BOINC relies on too much strstr(something, "ati") everywhere and the applications with ATI in the name are all deprecated now.

ATI isn't even a selection in the preferences anymore. How does that get missed?

It was gone for maybe 2 hours. BOINC relies on too much strstr(something, "ati") everywhere and the applications with ATI in the name are all deprecated now.

So, the answer to my question is "very easily". I can understand that.

I detached/reattached and still get 'no tasks available'

2/8/2012 10:07:28 PM Milkyway@Home Sending scheduler request: Project initialization.
2/8/2012 10:07:28 PM Milkyway@Home Requesting new tasks for CPU and GPU
2/8/2012 10:07:29 PM Milkyway@Home Scheduler request completed: got 0 new tasks
2/8/2012 10:07:29 PM Milkyway@Home Message from server: Project has no tasks available

Win7-64, HD5870, BOINC 6.10.58

---

There is a problem at present ... see:

"Separation updated to 1.00" in the News Forum

Regards
Zy

Right now it seems you can usually get CPU tasks and occasionally get a GPU task

I've been biting my tongue on the work availability issue, because the server is so blissfully stable.[ thanks guys !]

2/8/2012 9:41:25 PM | Milkyway@Home | Sending scheduler request: To fetch work.
2/8/2012 9:41:25 PM | Milkyway@Home | Requesting new tasks for ATI GPU
2/8/2012 9:41:29 PM | Milkyway@Home | Scheduler request completed: got 0 new tasks
2/8/2012 9:41:29 PM | Milkyway@Home | No work available

This isn't really a shock to me because I see that our global throughput has yet to peak. (0.7 Petaflops and counting :-) It does make me curious, though, as to whether is it possible to assess just what percent of requests for work are going unfilled by analyzing server logs, etc.

NOTE: I'm not talking about increasing WU limits, because in my experience, we're clearly not in danger of reaching them (I believe its at 40 per GPU?) Much of the time my client is living hand to mouth, often getting only one WU, finishing it, then getting one more, ad infinitum. Other times, it just runs dry.

In short, how close (or far) are we to having work supply keep up with demand?

... I'm not talking about increasing WU limits, because in my experience, we're clearly not in danger of reaching them (I believe its at 40 per GPU?) Much of the time my client is living hand to mouth, often getting only one WU, finishing it, then getting one more, ad infinitum. Other times, it just runs dry.

Mystery solved. It seems that this behaviour only occurs when i set my additional work buffer to 1 day or less. I set it to 5 days and voila! 20 WU's instantly. The WU cap of 20? = .014 days for a 6950, so i would expect any setting above that to keep me full. Somethings funky here.

Anyhoo... keep up the good work!

Actually I don't really know what fixed it; it isn't really fixed. I undeprecated the CAL stuff and both started getting sent out.

I think I fixed it.

Maximum CPU % for graphics
Frequency (in Hz) that should try to complete individual work chunks. Higher numbers may run slower but will provide a more responsive system. Lower may be faster but more laggy.

Both of those were set to a "non number" or something. Setting them back to a real number got me 24 tasks!

I think I fixed it.

Maximum CPU % for graphics
Frequency (in Hz) that should try to complete individual work chunks. Higher numbers may run slower but will provide a more responsive system. Lower may be faster but more laggy.

Both of those were set to a "non number" or something. Setting them back to a real number got me 24 tasks!

Those aren't related