I think this got lost in the other thread so, I made a new one.

As of 10PM PDT it is still acting as described below.

Can one of the guru's tell me if the below is another anomaly of the recent changes/issues.?

Notice the machine asks for 700K seconds of work, it only has 5 days of a 10 day cache, and the next request it asks for 0 seconds. Then 700K then 0.
Also the responses are different, sometimes it simply says you got nothing and sometimes it responds about nothing for AP, etc.

Aside from the fact that it is not receiving work, even though the Cricket graph is not maxed and work is available something else appears to be going on.

Note nothing has changed on the machine for over 1 year.

slws007.Staufferslandscape.com SETI@home 9/16/2011 10:41:54 AM Sending scheduler request: To fetch work. Requesting 754964 seconds of work, reporting 0 completed tasks
slws007.Staufferslandscape.com SETI@home 9/16/2011 10:41:59 AM Scheduler request succeeded: got 0 new tasks
slws007.Staufferslandscape.com SETI@home 9/16/2011 10:41:59 AM Message from server: No tasks sent
slws007.Staufferslandscape.com SETI@home 9/16/2011 10:41:59 AM Message from server: No tasks are available for Astropulse v5
slws007.Staufferslandscape.com SETI@home 9/16/2011 10:41:59 AM Message from server: No tasks are available for Astropulse v505
slws007.Staufferslandscape.com SETI@home 9/16/2011 10:41:59 AM Message from server: No tasks are available for the applications you have selected.
slws007.Staufferslandscape.com SETI@home 9/16/2011 11:00:35 AM Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 0 completed tasks
slws007.Staufferslandscape.com SETI@home 9/16/2011 11:00:40 AM Scheduler request succeeded: got 0 new tasks
slws007.Staufferslandscape.com SETI@home 9/16/2011 11:02:01 AM Sending scheduler request: Requested by user. Requesting 756989 seconds of work, reporting 0 completed tasks
slws007.Staufferslandscape.com SETI@home 9/16/2011 11:02:06 AM Scheduler request succeeded: got 0 new tasks
slws007.Staufferslandscape.com SETI@home 9/16/2011 11:02:06 AM Message from server: Project has no tasks available
slws007.Staufferslandscape.com SETI@home 9/16/2011 11:03:15 AM Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 0 completed tasks
slws007.Staufferslandscape.com SETI@home 9/16/2011 11:03:20 AM Scheduler request succeeded: got 0 new tasks
slws007.Staufferslandscape.com SETI@home 9/16/2011 11:06:35 AM Sending scheduler request: Requested by user. Requesting 0 seconds of work, reporting 0 completed tasks
slws007.Staufferslandscape.com SETI@home 9/16/2011 11:06:40 AM Scheduler request succeeded: got 0 new tasks
slws007.Staufferslandscape.com SETI@home 9/16/2011 11:11:45 AM Sending scheduler request: To fetch work. Requesting 758268 seconds of work, reporting 0 completed tasks
slws007.Staufferslandscape.com SETI@home 9/16/2011 11:11:50 AM Scheduler request succeeded: got 0 new tasks
slws007.Staufferslandscape.com SETI@home 9/16/2011 11:11:50 AM Message from server: No tasks sent
slws007.Staufferslandscape.com SETI@home 9/16/2011 11:11:50 AM Message from server: No tasks are available for Astropulse v5
slws007.Staufferslandscape.com SETI@home 9/16/2011 11:11:50 AM Message from server: No tasks are available for Astropulse v505
slws007.Staufferslandscape.com SETI@home 9/16/2011 11:11:50 AM Message from server: No tasks are available for the applications you have selected.

---

Dave

What happen between the work requests?

Because of the new changeset the estimated times of the WUs are too high.
And on my machine it was for CPU and GPU WUs the same (so I inserted again <flops> to my app_info.xml file and it's again how it should).

So I guess, now on your machine, if a few GPU WUs finished the whole estimated times are smaller, so the machine request new WUs.
If a CPU WU finish, the estimated times are again too high, so BOINC think your machine don't need new WUs.
If a few GPU WUs finished the whole estimated times are smaller, so the machine request new WUs.
..and again the same, and so on..


The answers of the scheduler server are because of high server load.
If you have an app_info.xml file with all what you would like to calculate and the project settings are also correct, you don't need to worry about.


- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC. - SETI@home needs your help. -

---

Just a couple of thoughs.
Is this computer set up to only do AP tasks?
What ver of BOINC used?
On some ver of BOINC it will not ask for work, if requested by the user and the request was too soon after the last request, So try not to hit the Update button too often.

It could be as the number AP tasks is at a high on the server status page and doesn't seem to be falling. That they may have stopped the d/load of AP due to the current BOINC extra long estimates problem.
I have not had any AP tasks d/loaded since early Tuesday.

Nothing happened between requests. The machine is AP on CPU only. Nothing completed, no GPU, no MB.

All of these work units were received before changeset. I had NNT set but released it to get new work.

---

Dave

Nothing happened between requests. The machine is AP on CPU only. Nothing completed, no GPU, no MB.

I guessed as much. Probably AP downloads are suspended until estimate problem fixed.

I agree that AP DL seems to be off, intentional or not.

But, I don't think that explains the 700k request followed by 0.

---

Dave

I agree that AP DL seems to be off, intentional or not.

But, I don't think that explains the 700k request followed by 0.

Try not clicking update for a while and see if it continues when BOINC does it's own requests.

Unfortunately it may have gone into long term backoff because it cannot get work.

The other option, is to maybe allow MB work on the cpu for a few days.

Which BOINC Version?
I have V6.12.33 and don't see seconds at the work requests.
I see only request work for CPU and/or NVIDIA GPU.

Maybe you should upgrade to the latest recommended V6.12.34 .

BTW. Between the work requests the S@h scheduler server want a 5 minutes : 3 seconds break (AFAIK), if earlier:
Scheduler request completed: got 0 new tasks
Not sending work - last request too recent: xxx sec


- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC. - SETI@home needs your help. -

---

Which BOINC Version?
I have V6.12.33 and don't see seconds at the work requests.
I see only request work for CPU and/or NVIDIA GPU.

Maybe you should upgrade to the latest recommended V6.12.34 .

BTW. Between the work requests the S@h scheduler server want a 5 minutes : 3 seconds break (AFAIK), if earlier:
Scheduler request completed: got 0 new tasks
Not sending work - last request too recent: xxx sec


- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC. - SETI@home needs your help. -

He is talking about a cpu only computer that only does AP tasks.
Therefore he doesn't need a Ver 6.n.x and he probably prefers to stay on 5.10.13 or similar.

That is how my PentM is set up. That is at my sons at the moment with no internet connection.

Ver 5.10.45. Has run great for over 1 year.

---

Dave

Why he should stay with V5.x?
V6.12.x (boinc.exe) use much less CPU time.

I would recommend all to upgrade.

I think the excuse that the last recommended versions don't work with PROXY is not longer correct/timely.
In past with the S@h router problem, I connected with 6.12.33 via HTTP PROXY to the S@h server.


- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC. - SETI@home needs your help. -

---

Ver 5.10.45. Has run great for over 1 year.

Yup, guessed as much. All you need if it hasn't got a gpu and probably more stable and reliable.

Yes. Very stable an reliable. Also it keeps all my machines the same. Some are domain controllers and cannot go beyond 5.10.45.

---

Dave

Though I might just point out that at the moment the pipeline is not blocked. Just d/loaded 43 MB tasks in just over 10 mins with no back-offs.

No AP tasks came through and as reported it other threads the APR for AP on this computer is way high and therefore if AP tasks were available when the three requests were made it should have selected them before MB tasks.

Aha. A small thought is slowly trying to fight it's way out of my Saturday-morning befuddled brain. Isn't one of the safeties built into DCF something like "do minimal work fetch when DCF is showing an absurd value"?

That might explain why my GTX 470 - with a DCF of 0.0139 - is only getting one SETI task at a time, and spending most of its time on GPUGrid, in defiance of Resource Share.

I might go and experiment after the next coffee....

Thats what i´m trying atm.
Thinking about resetting the debts.

---

With each crime and every kindness we birth our future.

There seems to be no shortage of MB tasks, have downloaded over 60 in the last few hours. And the pipeline is open, as in there have no back-offs, that I have seen, and the couple I watched reported speeds greater than 20 KBps.

edit] They are still, as you will have realised, with long completion estimates.

Thats what i´m trying atm.
Thinking about resetting the debts.

It's certainly not debt in my case. Ah, here's a smoking gun:

17/09/2011 10:15:08 | | [work_fetch] NVIDIA GPU: shortfall 28919.68 nidle 0.00 saturated 18600.32 busy 0.00 RS fetchable 300.00 runnable 700.00
17/09/2011 10:15:08 | SETI@home | [work_fetch] NVIDIA GPU: fetch share 1.00 LTD 0.00 backoff dt 0.00 int 0.00
17/09/2011 10:15:08 | | [work_fetch] No project chosen for work fetch
17/09/2011 10:15:39 | SETI@home | Computation for task 26jn11af.17695.2521.16.10.191_1 finished
17/09/2011 10:15:46 | | [work_fetch] Request work fetch: project finished uploading
17/09/2011 10:15:48 | SETI@home | [work_fetch] request: CPU (0.00 sec, 0.00 inst) NVIDIA GPU (1.00 sec, 1.00 inst)
17/09/2011 10:15:51 | SETI@home | Scheduler request completed: got 1 new tasks
17/09/2011 10:15:51 | SETI@home | [sched_op] estimated total NVIDIA GPU task duration: 327 seconds

I'm pretty sure that request for 1 second, when there's a near-30,000 second shortfall, is a DCF safety.

Edit - confirmed: I edited DCF by a factor of ten - took out a zero, so 0.013... became 0.13...

17/09/2011 10:23:28 | | [work_fetch] NVIDIA GPU: shortfall 25693.17 nidle 0.00 saturated 21826.83 busy 0.00 RS fetchable 300.00 runnable 700.00
17/09/2011 10:23:28 | SETI@home | [work_fetch] NVIDIA GPU: fetch share 1.00 LTD 0.00 backoff dt 0.00 int 0.00
17/09/2011 10:23:28 | SETI@home | [work_fetch] request: CPU (0.00 sec, 0.00 inst) NVIDIA GPU (25693.17 sec, 0.00 inst)
17/09/2011 10:23:28 | SETI@home | [sched_op] NVIDIA GPU work request: 25693.17 seconds; 0.00 GPUs

17.09.2011 11:22:01 [work_fetch] ------- start work fetch state -------
17.09.2011 11:22:01 [work_fetch] target work buffer: 864000.00 + 864000.00 sec
17.09.2011 11:22:01 [work_fetch] CPU: shortfall 6746683.04 nidle 0.00 saturated 578449.47 busy 54815.74 RS fetchable 800.00 runnable 800.00
17.09.2011 11:22:01 SETI@home [work_fetch] request: CPU (6746683.04 sec, 0.00 inst) ATI GPU (0.00 sec, 0.00 inst)

17.09.2011 11:22:01 SETI@home Sending scheduler request: To fetch work.
17.09.2011 11:22:01 SETI@home Reporting 4 completed tasks, requesting new tasks for CPU
17.09.2011 11:22:01 SETI@home [sched_op] CPU work request: 6746683.04 seconds; 0.00 CPUs
17.09.2011 11:22:01 SETI@home [sched_op] ATI GPU work request: 0.00 seconds; 0.00 GPUs
17.09.2011 11:22:09 SETI@home Scheduler request completed: got 65 new tasks
17.09.2011 11:22:09 SETI@home [sched_op] Server version 613
17.09.2011 11:22:09 SETI@home Project requested delay of 303 seconds
17.09.2011 11:22:09 SETI@home [sched_op] estimated total CPU task duration: 317490 seconds

Server code still very dumb.

---

With each crime and every kindness we birth our future.

Server code still very dumb.

What's dumb about that, in particular? You got 2/3rds of the available feeder tasks for that timeslice - it doesn't get much better than that.