tree 6584ceedeca9c46f9f1739f3694cef842ddf15d5
parent efcbc6e66d2e526bad4ad1c02e1ec2b29452b1da
author Willy Tarreau <w@1wt.eu> 1236327507 +0100
committer Willy Tarreau <w@1wt.eu> 1236327507 +0100
encoding latin1

[OPTIM] rate-limit: cleaner behaviour on low rates and reduce consumption

The rate-limit was applied to the smoothed value which does a special
case for frequencies below 2 events per period. This caused irregular
limitations when set to 1 session per second.

The proper way to handle this is to compute the number of remaining
events that can occur without reaching the limit. This is what has
been added. It also has the benefit that the frequency calculation
is now done once when entering event_accept(), before the accept()
loop, and not once per accept() loop anymore, thus saving a few CPU
cycles during very high loads.

With this fix, rate limits of 1/s are perfectly respected.