Joe,
I understand the objection. Here is why I think it isn't a problem.
Think of the extreme loading SETI has had lately.
Right now, we have a host connecting 1 hour/day, and when it connects
(day after day after day) it is in contention with those 50:1 servers.
Tomorrow, it's the same battle, because during the last 24 hours most
uploads have failed.
The next day, more of the same.
If changeset 18593 does what it should do, there will be fewer failed
uploads chewing up bandwidth -- more uploads will succeed because the
peak (ugly) load is reduced by 50:1.
Because more uploads complete, it is bad today, but by tomorrow the load
is reduced, and work goes through more easily.
That's the theory -- and I've seen this concept work in practice as
well. The model is RFC-2821 section 4.5.4.1, especially this paragraph:
A client SHOULD keep a list of hosts it cannot reach and
corresponding connection timeouts, rather than just retrying queued
mail items.
BOINC and SMTP are the same in this respect.
-- Lynn
Josef W. Segur wrote:
> David's changeset 18593 will provide the 50:1 reduction for that case
> once implemented, tested, released, and adopted by most users. What I
> was addressing is the side effects for hosts which can only connect
> intermittently. If uploads are halfway working as has frequently been
> the case at s...@h lately, the present situation is uncomfortable for both
> the project and participants, but even hosts which can only connect for
> an hour once a day or once a week are likely to be able to upload the
> completed results and download new work. With the 18593 change applying
> backoff to all uploads, those hosts will be far less likely to remain
> productive. I was suggesting a method to reduce that inequity for that
> specific subset of hosts, if such a change is not added the account
> owner might refuse to upgrade BOINC.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
