Hello Computer 6137511, control your machine

lovely, another anonymous user that cannot be contacted or identified

lovely, another anonymous user that cannot be contacted or identified

I'm curious how/why?

It's just a user who has hidden his/her computer(s).

Gruß,
Gundolf

lovely, another anonymous user that cannot be contacted or identified


I'm curious how/why?

It's just a user who has hidden his/her computer(s).

Gruß,
Gundolf

I suppose if my computer made that many errors I'd hide it too.
:-)
____________
-Dave (Two)

Before the icey finge of blame points its not me !

No, it's an anonymous host,
6137511.
So, don't worry ;-)
This host shouldn't get the normal amount of tasks, unless it delivers valid
results, IIRC!

In theory yes, unfortunately the quota system is (once again) not working for this host, it's allowed to get 100 tasks per day all the time and somehow it has even got 845 today, as you can see on the host's application details page.

No, it's an anonymous host,
6137511.
So, don't worry ;-)
This host shouldn't get the normal amount of tasks, unless it delivers valid
results, IIRC!

In theory yes, unfortunately the quota system is (once again) not working for this host, it's allowed to get 100 tasks per day all the time and somehow it has even got 845 today, as you can see on the host's application details page.

I've got one that is having problems with AP tasks, 74 of them. host 4840320, AP tasks But still allowed to d/load 100/day, probably because it processes MB tasks ok.

Looks like another modification needed in BOINC, so that it can stop downloads by task.

I've got one that is having problems with AP tasks, 74 of them. host 4840320, AP tasks But still allowed to d/load 100/day, probably because it processes MB tasks ok.

Looks like another modification needed in BOINC, so that it can stop downloads by task.

The quotas have been per app_version since April 2010. But the basic 100 comes from a single setting which applies to all kinds of tasks. Obviously if 100 is reasonable for MB, something like 10 would be for AP.

The real issue has always been how quickly the quota should grow. The present logic is a reported "success" doubles it if it is below 100 (capped to 100). Only errors recognized by the science application or core client can reduce the quota below the basic setting, since invalid tasks are reported as successes.

There have been several discussions on the boinc_dev mail list about the quota mechanism, but it remains in the condition that it can only protect against hosts which report all tasks from an app_version as errors.

Joe

With the host I reported if you look in Application details it is recorded;

AstroPulse v6 6.01 windows_intelx86
Number of tasks completed 0
Max tasks per day 101
Number of tasks today 1
Consecutive valid tasks 1
Average turnaround time 0.00 days

One success today but that is a "too much blanking"

Non of the other are recorded. The big problem there, IMO, is not counting the tasks completed when they are errors. Because the host has "completed" at least 74 tasks, but all are errors or "too much blanking". There should be some mechanism to spot this and decrease "Max tasks per day" and "too much blanking" should not increase "Max tasks per day".

...
Still it does not explain, why a host limited to 100 tasks per day (for a specific app) is able to get over 800.