Is there a bug in the Maximum daily WU quota?
10 Jul 2005 16:43:35 UTC
Topic 189515
(moderation:
Is there a bug in the Maximum daily WU quota?
This host http://einsteinathome.org/host/334723 managed to download nearly 600 WU's in one day. The host is created 1 Jul 2005 but there are Results from as early as 22 Jun on it.
Then you're really interested in a subject, there is no way to avoid it. You have to read the Manual.
Is there a bug in the Maximum daily WU quota?
)
More likely, it was one of those runaway times when boinc creates a new host, downloads, errors - then repeats that same process over and over, leaving a new host for each attempt.
The owner then probably merged all the hosts together, making it appear now that all those work units were downloaded to the same host id. And since boinc keeps the most recent host id when they're merged, any previous successful work would also now appear to have been done before the host existed.
At least one other person had
)
At least one other person had a similar problem check out this thread:
hogging wus
At one point almost all of wus were server state was "in progress" and client state was "new". I watched one of them climb from just over 400 to 580 over a period of days. If this were a case of merging computers the owner would have had to have done it hundreds of times.
Ziran, do you still have the message log from the day downloaded all those wus?
Also could you tell me please what is you setting for:
Connect to network about every
(determines size of work cache; maximum 10 days)
The host isn't mine. I found
)
The host isn't mine. I found it then i looked at the other hosts that are crunching the same WU as me.
Then you're really interested in a subject, there is no way to avoid it. You have to read the Manual.
There is another link further
)
There is another link further down the thread that matches your id.It is titled also thisone.
I was quite concerned about
)
I was quite concerned about this because there have been reports about the max daily quota being broken in SETI@Home. But I looked closely at this case. It appears that the problem arose because the user had created many hosts, each of which had gotten work, and then merged the hosts.
If anyone is having this problem (more than 8 WU per day per CPU being sent) and it is NOT due to merging hosts, please post to this thread.
Bruce
Director, Einstein@Home
Ziran & Keith Stanley: It
)
Ziran & Keith Stanley:
It looks to me like one host was requesting work that was being assigned to another. The first host never got the work and requested more, server did not see wus sent to the first host and tried to comply. It would be helpful to know what you did in the way of creating new host and merging old ones on July 1.