Can one of the regular gurus have a looksee at this computer's tasks, 33,000 seems a tad excessive for built in graphics ;-)

8572161

It's fairly obvious the pc is doing nothing with the tasks at the moment despite it polling every day, but how on earth can anyone amass that many tasks?

Phil.

---

Can one of the regular gurus have a looksee at this computer's tasks, 33,000 seems a tad excessive for built in graphics ;-)

8572161

It's fairly obvious the pc is doing nothing with the tasks at the moment despite it polling every day, but how on earth can anyone amass that many tasks?

Phil.

Yes this person has been mentioned before, I even sent him a PM but got no response.

Look here https://setiathome.berkeley.edu/forum_thread.php?id=69782 at the last few posts.

He also has another machine doing the same 8481944

He is obviously using something to fool the servers, what I don't know.

He’s not fooling the servers. He’s just doing something odd with his system or he’s got some hardware or software issue that’s ghosting all his tasks.

He downloads tasks. Ghosts them. His client thinks he has none. Asks for more, and on and on.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours

The question could be: Why the servers still sends new WU above the 100 limit to a non productive host?

---

There was someone a couple of years back who thought the object of SETI was to accrue as many tasks as possible and not return any results. He took some persuading of the error of his ways....

I suspect in this case it is an over-zealous AV software kicking off and dumping the tasks more or less as soon as they arrive

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

The question could be: Why the servers still sends new WU above the 100 limit to a non productive host?

Yes this is the question, 33000 tasks!! On that machine his "Max tasks per day" is 1 but 33000 days is 90 years ;-)

Why can that machine download more tasks without returning anything, that must be wrong.

One could understand an upper limit of say double the "normal allowance" of 100 + 100 per GPU to allow for ghosts, but 33k is just taking the proverbial - something along the lines of if a cruncher exceeded double the "normal max" then stop sending until the number on the cruncher was below half of the "normal max".....
Having looked at the server code I think it would be a fairly simple task to insert such a "sanity limit".

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

As I always said, the max number of WU on a host must be related to the host returning (valid) WU per day not a fixed limit line we have now.

---

But with ghosts. You’d have to wait ~6 weeks for them to time out before you can contribute to the project again.

---

Seti@Home classic workunits: 29,492 CPU time: 134,419 hours