I'm sitting here with no work, because the servers have been down for a while.

But, when I send an update request, I get back -

"Message from Server. Not sending work - last RPC too recent: 216 sec."

What is this all about? What does it matter that I sent a request 216 seconds ago? I'm sitting here with nothing to do. Why doesn't the system just send me something instead of being a Nanny (Ninny) and complaining that I sent in a request 215 seconds before (which also didn't get filled)? Or, if it doesn't have anything available to send, why doesn't it tell me that instead of making me mad with the stupid "too recent" message?

---

The reason you can't get work right now is that the servers are overloaded because there are several hundred thousand computers trying to contact the project. The mandatory 10 minute wait between RPC requests is designed to try and reduce this massive overload. Just let it do its thing. It will eventually get work.

---

A member of The Knights Who Say NI!
For rankings, history graphs and more, check out:
My BOINC stats site

The reason you can't get work right now is that the servers are overloaded because there are several hundred thousand computers trying to contact the project. The mandatory 10 minute wait between RPC requests is designed to try and reduce this massive overload. Just let it do its thing. It will eventually get work.

The ten minute wait must have been designed by someone with no know3ledge of statistics, or of computer wait queues.

Also, why not produce a response message with some better clarity, instead of the maddening "too recent" message?

I'm not angry at you personally, it just sounds like I am - sorry. As an engineer, I detest bad design, and this sure looks like it to me.

---

As an engineer, I detest bad design, and this sure looks like it to me.

Then the whole use of the Upload or Download terms must drive you nuts. LOL

did I just upload this message or was the message downloaded????

As an engineer, I detest bad design, and this sure looks like it to me.

Then the whole use of the Upload or Download terms must drive you nuts. LOL

did I just upload this message or was the message downloaded????

I wonder if Scotty had this problem? :)

---

The ten minute wait must have been designed by someone with no know3ledge of statistics, or of computer wait queues.

More likely by someone with much past experience with this project and full understanding of what happens after an outage and what happens when someone discovers a tool to bombard the servers with way too many requests.

Also, why not produce a response message with some better clarity, instead of the maddening "too recent" message?

Very clear response.
"I just talked to you. Nothing new since a few minutes ago. Call me later."
BOINC understands. It will call back in 10 minutes.

---

Yes, but is it too hard to make the system ready for so much people?
Remember: they want someting from US -not we from THEM
And: In seti-classic i have _sometimes_ problems, but now I'm more disabled then make my credits. :-(
I just can tell that I'm very, very anoyed about this.

If I go to the next church or Red Cross Station whith several bucks in my hand to spend I _never_ will got such a reply as "sorry, not this moment -come back tomorrow, next week or moth -better NEVER!" :-P

i have several discussions with my wife and friends why my computers will work 24/7, but my argument for the last month is -I didn't know! :-(

regards
John

---

Yes, but is it too hard to make the system ready for so much people?

In a word, yes. You try listening to 100,000 people all shouting at once.

If I go to the next church or Red Cross Station whith several bucks in my hand to spend I _never_ will got such a reply as "sorry, not this moment -come back tomorrow, next week or moth -better NEVER!" :-P

Bad analogy, unless of course there are 100,000 people in line waiting to give them money. If you were the only person there, OF COURSE there is no problem.

If you were the only BOINC user trying to update at SETI, there wouldn't be a problem either.

But you're not. You're competing with a hundred thousand others to get some attention.

---

Yes, but is it too hard to make the system ready for so much people?
Remember: they want someting from US -not we from THEM
And: In seti-classic i have _sometimes_ problems, but now I'm more disabled then make my credits. :-(
I just can tell that I'm very, very anoyed about this.
If I go to the next church or Red Cross Station whith several bucks in my hand to spend I _never_ will got such a reply as "sorry, not this moment -come back tomorrow, next week or moth -better NEVER!" :-P
i have several discussions with my wife and friends why my computers will work 24/7, but my argument for the last month is -I didn't know! :-(
regards John

JOHN you are telling untruths! Chruch's DO close and when they are you CANNOT give donations to them! The Red Cross DOES close, come on down to the office around midnite most nights, the guard will have you arrested if you do not leave!
That being said....the problem is that the project has to support all people not just those with cable of dsl connections, but those on dial-up too. That means that when you and I are banging on the doors trying to get our units up and downloaded the dial-up people have NO CHANCE of getting thru. Soooo a delay was instituted to prevent those banging on the door people. Gives everyone an equal shot at connecting and treats everyone the same. What was happening was in effect a DOS or Denial of Service attack. We highspeed users were tying up so much bandwidth that no one could get thru.

---

Back in the early days of BOINC, there was a few (or many) ill-behaving clients that kept hitting the servers. In essence, they had a DDoS occuring. Because of that, they implimented the 10 minute minimum delay.

---