Recently I've been seeing a lot of these messages from SETI scheduler after I download one WU to the cache:

Message from server: Not sending work - last RPC too recent: 307 sec

Other projects (EAH, PAH) don't display this behaviour. As I am on a dial-up and usually connect only once or twice per day, I seldom have more than one SETI WU in the cache, though I could have done 6 inbetween connections. As a result I had to compensate and up the cache size to get more work from the other projects.

I understand that new WU denial after a recent download is designed to prevent DoS attacks and emptying of the splitted WUs, but in the end it really robs the project of CPU time that it it could hae utilised...

Stanislav.

---

---
<img border="0" src="http://boinc.mundayweb.com/one/stats.php?userID=875&amp;trans=off" />
Everything is just <A HREF="http://heim.ifi.uio.no/~stanisls/fysisk/">A Question of Physics</A>

I've got the same problem very often.
Only with Seti and only using one of my computers.
Other machines run without any problems as well as every other projects doesn't react like the Seti-Scheduler.

Don't know why.

Greetings
Stefan

---

<img src="http://www.boincstats.com/stats/banner.php?cpid=710c1e51b47b1aa3c4b24b13251cb271"> <img src="http://www.boincstats.com/stats/teambanner.php?teamname=armageddon">

> I've got the same problem very often.
> Only with Seti and only using one of my computers.
> Other machines run without any problems as well as every other projects
> doesn't react like the Seti-Scheduler.
>
> Don't know why.

Because, especially after an outage, people like to hit the "update" button every few seconds. That really hammers the scheduler, so SETI has code in place that penalizes scheduler abuse.

It does cause some issues if you tightly control your connection.

If you see that happen, just wait ten minutes and try again.

---