Just been looking thru my `pending` WU's. Noticed one is really lagging so had a look thru the other hosts crunching it, and found this guy has got over 300 WU's downloaded for 1 of his machines.

However judging by fact that he has got WU's returned today, which were sent in last day or so, means these 100 WU's are not even being touched. Will have to wait til it times out, but they need to stop this hoarding ability. It really annoys me that people do this, i know its not a competition etc, but this is just really annoying.

*edit - learned to count and updated number of WU's this guy has `hoarded`

---

> Just been looking thru my `pending` WU's. Noticed one is really lagging so had
> a look thru the other hosts crunching it, and found this guy has got over 300
> WU's downloaded for 1 of his machines.
>
> However judging by fact that he has got WU's returned today, which were sent
> in last day or so, means these 100 WU's are not even being touched. Will have
> to wait til it times out, but they need to stop this hoarding ability. It
> really annoys me that people do this, i know its not a competition etc, but
> this is just really annoying.
>
> *edit - learned to count and updated number of WU's this guy has `hoarded`

And it'll probably get worse once SETI Classic shuts down.
That Classic mindset will take some time to break.

Dominique

---

I can only assume they tried a really high setting for something and it downloaded all that and they went, OOPS..

Ahh well.. would be nice if they did limit it. Maximum of X amount of WU per download etc

---

>
> Ahh well.. would be nice if they did limit it. Maximum of X amount of WU per
> download etc
>

In seti, you can max download 20 wu/RPC, and 100 wu/day per host.

In seti, you can max download 20 wu/RPC, and 100 wu/day per host.
=========

I thought that 50 was the Max per Host per day ... ??? ... Thats all I've ever been able to download to a host in a day ...

>
> I thought that 50 was the Max per Host per day ... ??? ... Thats all I've ever
> been able to download to a host in a day ...
>

This was increased to 100 last week in December.

> >
> > I thought that 50 was the Max per Host per day ... ??? ... Thats all I've
> ever
> > been able to download to a host in a day ...
> >
>
> This was increased to 100 last week in December.
>

Probably explains what this user did. Still means he's taken 300+ WU away from us til the system times out. 100 sounds very excessive, especially for a single machine.. I mean my fastest machine does a WU in about 5 hours, so that means 100 WU's would take upto 500 hours which is 20 days.. this guy has 300+ and when WU have a life of 14 days you can see why i think this is excessive :)

---

> > >
> > > I thought that 50 was the Max per Host per day ... ??? ... Thats all
> I've
> > ever
> > > been able to download to a host in a day ...
> > >
> >
> > This was increased to 100 last week in December.
> >
>
> Probably explains what this user did. Still means he's taken 300+ WU away from
> us til the system times out. 100 sounds very excessive, especially for a
> single machine.. I mean my fastest machine does a WU in about 5 hours, so that
> means 100 WU's would take upto 500 hours which is 20 days.. this guy has 300+
> and when WU have a life of 14 days you can see why i think this is excessive
> :)
>
The limit is per host, not per CPU. S@H has a few crunchers with 10 or more CPUs per host that are very fast machines. Figure 10 CPUs at 10 WUs / day each = 100 WUs / day for that host. If the limit were per CPU, it could safely be set to about 20, and not affect anybody.

---

BOINC WIKI

> > >
> > > I thought that 50 was the Max per Host per day ... ??? ... Thats all
> I've
> > ever
> > > been able to download to a host in a day ...
> > >
> >
> > This was increased to 100 last week in December.
> >
>
> Probably explains what this user did. Still means he's taken 300+ WU away from
> us til the system times out. 100 sounds very excessive, especially for a
> single machine.. I mean my fastest machine does a WU in about 5 hours, so that
> means 100 WU's would take upto 500 hours which is 20 days.. this guy has 300+
> and when WU have a life of 14 days you can see why i think this is excessive
> :)
I have machines that do a unit in about 2 hours. That means 12 per day and then if I play with my cache I could need upto 10 days worth. That would put me at the 100 limit for a couple of days or so.
There was a hard limit of a 10 day cache put on a short while back. So the guy with 300 units either will get 300 more if his cache is set that high, and his machine can do that, or more likely, he will get only a 10 day max cache worth.

---

I'm not sure if the maximum cache is 50 or 100 or somewhere in between. I got an 8 processor Xeon box running Seti Boinc 24x7. It turns out around 32 work units/day. I set the cache limit to 3 days and now have 70 work units either running or waiting.

This guy has a bog standard machine returning WU at a slower pace then my machine :)

He has a few machines, this being his fastest, but all 300 WU were assigned to this one host. No chance its gonna be able to process the data so quickly.

I know there will be configurations out there that can do this kinda processing really quick, just a shame the client isnt able to accurately see the users machine is taking too much.

Aint a major biggie, it will eventually get swallowed back into the system again.

---

Just a thought here and I do understand what you are saying but could this be someone that was having problems and did a reset? perhaps a few times? Ive read some posts and I do seem to remember people saying do a reset to fix some problems. It does seem large and probably is holding up some of the process in getting caught up. *shrug*

---

<a href="http://www.teampicard.net"><img src="http://boinc.mundayweb.com/seti2/stats.php?userID=2205&amp;trans=off"></a>

> Just a thought here and I do understand what you are saying but could this be
> someone that was having problems and did a reset? perhaps a few times? Ive
> read some posts and I do seem to remember people saying do a reset to fix some
> problems. It does seem large and probably is holding up some of the process in
> getting caught up. *shrug*
>

Another explanation could be that he's testing the software, so, he backs up stuff to an old directory, tries a new version, gets results from software testing, finds a bug, and reverts back to his saved backup which doesn't contain any 'recently downloaded' units.

> > I thought that 50 was the Max per Host per day ... ??? ... Thats all I've
> ever
> > been able to download to a host in a day ...
> >
>
> This was increased to 100 last week in December.
========

@ Ingleside

I didn't know that Ingleside, it doesn't make much sense to me though to increase the limit to 100 per day per host per day to satisfy the very few clients out there that can actually do 100 WU's per day, all their doing now is allowing the rogue computers out there to waste more WU's.

The old way 14 day Max & 50 per day = 700 WU's wasted by a rouge computer.
Now the new way @ 100 per day will = 1400 Wasted WU's over a 14 day period.
So all they've done is allow any rogue computers to waste twice as many WU's ... ???

Personally I think once they shut down Set Classic with this sort of download scheme there is going to be a ton of wasted WU's & backlog of pending credit WU's for everybody ... !!!

> Personally I think once they shut down Set Classic with this sort of download
> scheme there is going to be a ton of wasted WU's & backlog of pending
> credit WU's for everybody ... !!!
>

We agree on something. I think I pretty much said that way back.

Dominique

---

> > This was increased to 100 last week in December.
> ========
>
> @ Ingleside
>
> I didn't know that Ingleside, it doesn't make much sense to me though to
> increase the limit to 100 per day per host per day to satisfy the very few
> clients out there that can actually do 100 WU's per day, all their doing now
> is allowing the rogue computers out there to waste more WU's.
>

My suggestion (and supplied source code) was for 20 WUs per CPU (or pretend CPU ala HT), but wasn't adopted.

The cache should be limited to 5 days maximum.

---

Red Bull Air Racing

Gas price by zip at Seti

> The cache should be limited to 5 days maximum.

Why?
As long as the Work Unit results are returned within 14 days what's the problem?

---

Grant
Darwin NT

As long as the Work Unit results are returned within 14 days what's the problem?
=========

Grant, the problem is some people only cache a few WU's at a time & they expect every one else to do the same thing so they can have their precious credits instantly. Thats the Seti Classic Mindset working on them, do a WU and get 1 credit instantly.

I don't worry about them and I keep enough work cached for 4 or 5 days so if theres a unexpected burp in the server I can keep on crunching. I look at it this way, I have WU's Pending that have been sitting for 3 & 4 weeks already so I don't see where I'm the one holding up anybody for more than a few days at the most.

Going along with the post I beleive the basic reason is because if a person has a large farm or fast comps and then a problem happens then they end up holding up the whole system with 100's if not 1000's of units.
I'm new but I would agree with the thought process of 7 day max cache personally.

The problem right now as I see it is that the systems are not getting the correct amount of work per say. Mine says WU should take around 4.5 hours per and they take actually 3.5 pretty steady.

Other than that I just cant think of any reason that would benefit the project letting people load up 14 days of cache if units need to be returned in 14 days, but I can think of a whole bunch of neg's.

---

<a href="http://www.teampicard.net"><img src="http://boinc.mundayweb.com/seti2/stats.php?userID=2205&amp;trans=off"></a>