I downloaded version 7.16.5 (x64) a day or so ago, and since then the Event Log has been displaying the message "Project requested delay of 3636 seconds" repeatedly.
That is all it seems to do.
How do I make it a little more sensible?

I think that is just what it does these days. I see the same thing (different times) on other projects.

It won't send you any Windows tasks because there aren't any.

Thank you very much. It is presumably only an addition to the Event Log under version 7.16.5 (x64), and does not affect the operation of BOINC. Please confirm that this is so, if you are able to.,

7.16.5 works fine for me under Win7 64-bit, and 7.16.6 under Linux.

Do you get the messages "Project requested delay of xxxx seconds" ?

[quote]"Project requested delay of 3636 seconds" repeatedly.

FYI the 3636 second is the standard 1 hour back-off

Currently getting this response under Linux and BOINC 7.16.6. Status page says there are 1744 jobs available. No other relevant-looking messages.

---

Currently getting this response under Linux and BOINC 7.16.6. Status page says there are 1744 jobs available. No other relevant-looking messages.

Were there similar messages before you upgraded to Ubuntu 20.04?

Did you upgrade over 19.10 or did you do a clean install of 20.04?

The solution is obviously to post to the forum, because I now have a task running...

---

This is a clean install of Lubuntu 20.04. CPDN now running happily. The first job started spontaneously, at random. A second started immediately I gave it another core.

There were no similar messages in 19.04.

---

I am also curious about an inability to get any tasks. I have a new-ish computer purchased in 2019, running Windows 10. I have allocated twice the resource share to Climate Prediction than any other project. 6 months ago I was receiving tasks, and completing in a week or two tasks that had a deadline a year away. It's been several months since I've received any new tasks, despite dozens of "update requests- often several times a day (for months now). Any theories as to why I suddenly get no tasks when I've successfully completed tasks ahead of schedule- demonstrating my computer is up to the job of crunching this project. I even tried dropping all other projects, So there would be no competition with "Climate Prediction."

I am also curious about an inability to get any tasks. I have a new-ish computer purchased in 2019, running Windows 10.

OK, I can spare the moderators the trouble.
There are no Windows tasks (wah2) at the moment, and none on the horizon that anyone knows about.
https://www.cpdn.org/server_status.php

The only ones are for Linux now (32-bit by the way).

There are no Windows tasks (wah2) at the moment, and none on the horizon that anyone knows about.

Though as I posted a few days ago,

#869 Micro-batch of 15 pnw tasks went out on the 29th April.

Sometimes these micro-batches are the herald of a larger release though I have seen nothing on the moderator communications to suggest this on this occasion. Three of the fifteen have completed. The other twelve have all gone to a machine with an average turn around time of 65 days so even if it is the herald of a larger batch we may have to wait a while.

While we are on the subject, this is supposed to be an active hurricane season.
I hope that OpenIFS can make a contribution to the methodology of prediction.

There are no Windows tasks (wah2) at the moment, and none on the horizon that anyone knows about.

Though as I posted a few days ago,

#869 Micro-batch of 15 pnw tasks went out on the 29th April.

Sometimes these micro-batches are the herald of a larger release though I have seen nothing on the moderator communications to suggest this on this occasion. Three of the fifteen have completed. The other twelve have all gone to a machine with an average turn around time of 65 days so even if it is the herald of a larger batch we may have to wait a while.

There should be some way to better spread these small test batches (if that’s what this micro-batch was) around so that they don’t all get sucked into this kind of black hole machine. Otherwise this will become more and more of a problem as processors get ever larger numbers of cores.

---

There should be some way to better spread these small test batches (if that’s what this micro-batch was) around so that they don’t all get sucked into this kind of black hole machine. Otherwise this will become more and more of a problem as processors get ever larger numbers of cores.

I agree. Usually this is done via the testing site. I have I suspect the slowest machine on there and on that these tasks would take about 20 days. The machine I use for testing site runs 24/7 which the machine with the tasks clearly doesn't as it is a lot faster yet still takes 65 days to turn tasks around..

I don't know why these were sent out on the main site rather than testing. The other option if there is a good reason for using the main site for them would be to send out say 100 instead of 15 which would hopefully get enough data back quickly.

There should be some way to better spread these small test batches (if that’s what this micro-batch was) around so that they don’t all get sucked into this kind of black hole machine. Otherwise this will become more and more of a problem as processors get ever larger numbers of cores.

I agree. Usually this is done via the testing site. I have I suspect the slowest machine on there and on that these tasks would take about 20 days. The machine I use for testing site runs 24/7 which the machine with the tasks clearly doesn't as it is a lot faster yet still takes 65 days to turn tasks around..

I don't know why these were sent out on the main site rather than testing. The other option if there is a good reason for using the main site for them would be to send out say 100 instead of 15 which would hopefully get enough data back quickly.

Dave,

There is another reason a system can seem to take an age to send stuff back, which you may or may not have considered. I run CPDN on an i7-6700K and a Ryzen 3700X system, both of which take about 7.5 days to run one HadAM4h task but which seem to take a month or more to turn jobs around. In my case this is because if I'm not careful CPDN will send me as many tasks as I have "CPUs" available to BOINC but I only run one (i7) or two (Ryzen) CPDN tasks at once! Perhaps that machine that snagged all the WIndows jobs hit the same problem?...

I wish every BOINC site had the facility they've implemented at WCG whereby you can say "I never want more than N of these on my machine at once" and it won't send work that would exceed that. The alternative, of course, would be if the BOINC client respected the max_concurrent option and sent that as the number of CPUs instead of the actual number, which would offer the same sort of control!

Cheers - Al.

---