-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11 Apr 2006, at 09:15, Matthew Toseland wrote:
Which requests should count for load limiting?
Load limiting is the process whereby if we get a RejectedOverload or a
timeout we reduce the rate at which we send (locally originated)
requests, and if we don't, we increase it.
The original intention I think, based loosely on the TCP-over-Ethernet
metaphor, was to only count locally originated requests. So if we
get a
timeout on any other request, this doesn't affect the rate at which we
send requests.
Is this the best option? It is perhaps closest to "propagate the load
back to the originator"? But maybe more information - counting other
requests - would be better?
We should not change this, we need to keep it simple - only
introducing further complexity if there is a *clear* justification.
I don't see a clear justification here.
Ian.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (Darwin)
iD8DBQFEO/iLQtgxRWSmsqwRApq3AJ0brx1vu7aK1WtZhgyxl95wmxhl2wCeMaVm
i9RW9QqbzcE2vpalivRTryY=
=SM3m
-----END PGP SIGNATURE-----
_______________________________________________
Devl mailing list
[email protected]
http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
