[Devel] rand function in config file

[Klaus Darilion]

Hendrik Scholz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi Klaus!
> 
> Klaus Darilion wrote:
>> I once thought of having a mechanism which checks the input queue of the
>> sockets. If it reaches a certain level, some messages get rejected, e.g.:
> ...
>> reject REGISTER
> 
> Sampling messages during a timeframe and blocking messages after a
> certain threshold was exceeded could be a very bad idea.
> Rejected devices will retransmit or retry registering after a fixed
> time. If your clients are either all the same or all use the same timer
> you'll end up with yet another load peak after the retry timer fires.
> 
> For the SER ratelimit module we have RED (random early detection).
> In a nutshell it samples the number of messages and for the next
> timeframe drops every n-th message in order to get the total number

drop (causes retransmissions) or reject?

regards
klaus

> allowed through below the threshold.
> 
> We are also looking into hacking ratelimit up or rewriting it
> to fit more needs.
> We also looked into writing a 'random' function to be able to
> write custom Retry-After headers and even out the load peaks.
> 
> There is an ongoing 'ratelimit revamp' thread on serdev@
> 
> Just my $.02,
>  Hendrik
> 
> - --
> Hendrik Scholz - <hscholz at raisdorf.net> - http://www.wormulon.net/
> drag me, drop me - treat me like an object
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (FreeBSD)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> 
> iD8DBQFGAUuj4Wmz+z2IPqARArJyAKCTdq7ursyQLLMN6TrLpTfKhs/KxQCgyrMl
> TL6hsQYjG2wiUFmo41yRoX0=
> =aGgN
> -----END PGP SIGNATURE-----