decay.yo (995B)
1 conf(decay - Levelling out activity of a back end) 2 (To make sure that a 'spike' of activity doesn't 3 influence the perceived load of a back end forever, you may 4 specify a certain decay. E.g, the statement tt(decay 10) makes 5 sure that the load that crossroads computes for this back end (be 6 it in seconds or in bytes) is decreased by 10% each time that 7 bf(an other) back end is hit. Decays are not applied to the count 8 of concurrent connections. 9 10 This means that when a given back end is hit, then its usage data 11 of the transferred bytes and the connection duration are updated 12 using the actual number of bytes and actual duration. However, 13 when a different back end is hit, then the usage data are 14 decreased by the specified decay. ) 15 (tt(decay) em(number), where em(number) is a percentage that 16 decreases the back end usage data when other back ends are 17 hit.) 18 (0, meaning that no decay is applied to usage statistics.)