Hi Alex, On Sat, Jan 07, 2023 at 06:31:40PM +0100, Aleksandar Lazic wrote: > > > On 07.01.23 10:38, Willy Tarreau wrote: > > Hi, > > > > HAProxy 2.8-dev1 was released on 2023/01/07. It added 206 new commits > > after version 2.8-dev0. > > [snipp] > > Any chance to add this patch to 1.8? > > [PATCH] MINOR: sample: Add bc_rtt and bc_rttvar > https://www.mail-archive.com/[email protected]/msg42962.html > > What's the plan for this feature request?
We can merge it. I think the reason it's been let rotting is that it seems from its commit message to be quite strongly tied to the EWMA stuff and in my opinion it should not. As you mentioned in the message above, it has plenty of use cases, one of which is simply logging. Some may want it to be backported just for logging and we don't want to put such confusing references there. So let's just adjust the commit message to be more factual about what it does (i.e. provide bc_rtt and bc_rtt_avg to report the RTT measured over a TCP backend connection) and be done with it. > Server weight modulation based on smoothed average measurement > https://github.com/haproxy/haproxy/issues/1977 > > which looks a per-requirement for > > New Balancing algorithm (Peak) EWMA > https://github.com/haproxy/haproxy/issues/1570 I really have no status for all this. Feature requests accumulate facter than bug reports and the only cases where I create one is to make sure to dump what I have in mind after a discussion so that I have somewhere to look for the details when trying to get back to it :-/ Cheers, Willy
