On Tue, 04 Jul 2023, Chuck Lever wrote: > From: Chuck Lever <chuck.lever@xxxxxxxxxx> > > To get a sense of the average number of transport enqueue operations > needed to process an incoming RPC message, re-use the "packets" pool > stat. Track the number of complete RPC messages processed by each > thread pool. If I understand this correctly, then I would say it differently. I think there are either zero or one transport enqueue operations for each incoming RPC message. Is that correct? So the average would be in (0,1]. Wouldn't it be more natural to talk about the average number of incoming RPC messages processed per enqueue operation? This would be typically be around 1 on a lightly loaded server and would climb up as things get busy. Was there a reason you wrote it the way around that you did? NeilBrown
