Currently "didn't need", "redundant result", "cancelled" and stuff like that reduce the daily quota of the hosts, server side issues shouldn't influence the daily quota.

==========================================

The current quota systems allows hosts to always have the full quota with only 2% (!!!) good results :

void SCHEDULER_REPLY::got_good_result() {
host.max_results_day *= 2;
if (host.max_results_day > config.daily_result_quota) {
host.max_results_day = config.daily_result_quota;
}
}

void SCHEDULER_REPLY::got_bad_result() {
host.max_results_day -= 1;
if (host.max_results_day < 1) {
host.max_results_day = 1;
}
}

This allows crunchers to choose the more "lucrative" results and abort the ones with a lower credits/time ratio.

The bad-hosts penalty should be way more efficient :

void SCHEDULER_REPLY::got_good_result() {
host.max_results_day += 1;
if (host.max_results_day > config.daily_result_quota) {
host.max_results_day = config.daily_result_quota;
}
}

void SCHEDULER_REPLY::got_bad_result() {
host.max_results_day /= 2;
if (host.max_results_day < 1) {
host.max_results_day = 1;
}
}

==========================================

Those two issues should be solved in the same release. Some projects cancel large batches of results frequently so improving the bad-hosts issue requires that server-side issues cannot make a host "bad".


p.s.: I did report the 2% problem already somewhere long time ago but I didn't find where it was