Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id CB2CF200B26 for ; Mon, 13 Jun 2016 07:51:23 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id BEFB0160A5C; Mon, 13 Jun 2016 05:51:23 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 148E4160A2C for ; Mon, 13 Jun 2016 07:51:22 +0200 (CEST) Received: (qmail 7312 invoked by uid 500); 13 Jun 2016 05:51:21 -0000 Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@kafka.apache.org Delivered-To: mailing list dev@kafka.apache.org Received: (qmail 7301 invoked by uid 99); 13 Jun 2016 05:51:21 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Jun 2016 05:51:21 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 07A5C2C1F61 for ; Mon, 13 Jun 2016 05:51:21 +0000 (UTC) Date: Mon, 13 Jun 2016 05:51:21 +0000 (UTC) From: "aarti gupta (JIRA)" To: dev@kafka.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (KAFKA-3811) Introduce Kafka Streams metrics recording levels MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 13 Jun 2016 05:51:24 -0000 [ https://issues.apache.org/jira/browse/KAFKA-3811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326855#comment-15326855 ] aarti gupta commented on KAFKA-3811: ------------------------------------ Yes indeed, as per http://www.brendangregg.com/blog/2014-06-09/java-cpu-sampling-using-hprof.html Tried to do something similar using simpleBenchmark (on a different fix) and yourkit profiler as [~gfodor] mentions below, here https://github.com/apache/kafka/pull/1446#issuecomment-225488213, but not convinced that the results mean anything conclusive. thoughts/suggestions on a repeatable/consistent toolset Like the idea of 3>>Add a general purpose feature to the metrics library and use it across the producer, consumer, and streams. But before we refactor the existing library want a reproducible test, any suggestions on a sceanrio other than SimpleBenchmark? > Introduce Kafka Streams metrics recording levels > ------------------------------------------------ > > Key: KAFKA-3811 > URL: https://issues.apache.org/jira/browse/KAFKA-3811 > Project: Kafka > Issue Type: Improvement > Components: streams > Reporter: Greg Fodor > Assignee: aarti gupta > Attachments: Muon-Snapshot.zip, Muon-latency.zip, screenshot-1.png, screenshot-latency.png > > > Follow-up from the discussions here: > https://github.com/apache/kafka/pull/1447 > https://issues.apache.org/jira/browse/KAFKA-3769 > The proposal is to introduce configuration to control the granularity/volumes of metrics emitted by Kafka Streams jobs, since the per-record level metrics introduce non-trivial overhead and are possibly less useful once a job has been optimized. > Proposal from guozhangwang: > level0 (stream thread global): per-record process / punctuate latency, commit latency, poll latency, etc > level1 (per processor node, and per state store): IO latency, per-record .. latency, forward throughput, etc. > And by default we only turn on level0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)