I submitted the original 2.8 cost-based FCQ patch (thanks to community members for porting to other branches). We've been running with it since early 2019 on all clusters. Multiple clusters run at a baseline of ~30k+ ops/sec with some bursting over 100k ops/sec.
If you are looking at the overall average qtime, yes, that metric is expected to increase and means it's working as designed. De-prioritizing write heavy users will naturally result in increased qtime for those calls. Within a bucket, call N's qtime is the sum of the qtime+processing for the prior 0..N-1 calls. This will appear very high for congested low priority buckets receiving a fraction of the service rate and skew the overall average. On Fri, Oct 30, 2020 at 3:51 PM Fengnan Li <loyal...@gmail.com> wrote: > Hi all, > > > > Has someone deployed Cost Based Fair Call Queue in their production > cluster? We ran into some RPC queue latency degradation with ~30k-40k rps. > I tried to debug but didn’t find anything suspicious. It is worth > mentioning there is no memory issue coming with the extra heap usage for > storing the call cost. > > > > Thanks, > > Fengnan > >
