[jira] [Resolved] (KAFKA-3826) Sampling on throughput / latency metrics recording in Streams
[ https://issues.apache.org/jira/browse/KAFKA-3826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthias J. Sax resolved KAFKA-3826. Resolution: Duplicate > Sampling on throughput / latency metrics recording in Streams > - > > Key: KAFKA-3826 > URL: https://issues.apache.org/jira/browse/KAFKA-3826 > Project: Kafka > Issue Type: Bug > Components: streams >Reporter: Guozhang Wang >Priority: Major > Labels: architecture, performance > > In Kafka Streams we record throughput / latency metrics on EACH processing > record, causing a lot of recording overhead. Instead, we should consider > statistically sampling messages flowing through to measures latency and > throughput. > This is based on our observations from KAFKA-3769 and KAFKA-3811. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (KAFKA-3826) Sampling on throughput / latency metrics recording in Streams
[ https://issues.apache.org/jira/browse/KAFKA-3826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Guozhang Wang resolved KAFKA-3826. -- Resolution: Fixed This is been done as part of KAFKA-5152. > Sampling on throughput / latency metrics recording in Streams > - > > Key: KAFKA-3826 > URL: https://issues.apache.org/jira/browse/KAFKA-3826 > Project: Kafka > Issue Type: Bug > Components: streams >Reporter: Guozhang Wang > Labels: architecture, performance > > In Kafka Streams we record throughput / latency metrics on EACH processing > record, causing a lot of recording overhead. Instead, we should consider > statistically sampling messages flowing through to measures latency and > throughput. > This is based on our observations from KAFKA-3769 and KAFKA-3811. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
