Hi Tobias, On Fri, Feb 20, 2015 at 03:58:10PM +0100, Tobias Feldhaus wrote: > Hey guys, > > thank you very much for the details. We moved from a simple perl script > that produced new connections all the time for pushing the data onto the > KAFKA message queue to an intelligent producer written in Erlang some > months ago. This producer keeps the connections alive and therefore the > statistics do not get updated:
(...) OK thanks for confirming this was the cause. Out of curiosity, how often does your producer write to the socket, how much data each time, etc ? I'm asking because I think that the loss of the continuous stat often is sad in situations like yours, and at the same time I'm thinking that maybe we could managed to force *some* of the transfers to wake the session up to update the counters once in a while. The principle could be based on volume, number of reads or anything that we already have, we just have to find the correct metric that serves the purpose well and that doesn't affect performance. Thanks, Willy
