Return-Path: X-Original-To: apmail-samza-dev-archive@minotaur.apache.org Delivered-To: apmail-samza-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8C4091873E for ; Wed, 17 Jun 2015 18:26:09 +0000 (UTC) Received: (qmail 57397 invoked by uid 500); 17 Jun 2015 18:26:09 -0000 Delivered-To: apmail-samza-dev-archive@samza.apache.org Received: (qmail 57338 invoked by uid 500); 17 Jun 2015 18:26:09 -0000 Mailing-List: contact dev-help@samza.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@samza.apache.org Delivered-To: mailing list dev@samza.apache.org Received: (qmail 57326 invoked by uid 99); 17 Jun 2015 18:26:09 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Jun 2015 18:26:09 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id A5190CE872 for ; Wed, 17 Jun 2015 18:26:08 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 4.001 X-Spam-Level: **** X-Spam-Status: No, score=4.001 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, KAM_LAZY_DOMAIN_SECURITY=1, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id 7Z0wI1Bq6cNZ for ; Wed, 17 Jun 2015 18:25:58 +0000 (UTC) Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 3B42A43AC7 for ; Wed, 17 Jun 2015 18:25:58 +0000 (UTC) Received: by wiwd19 with SMTP id d19so167279wiw.0 for ; Wed, 17 Jun 2015 11:25:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=T4mAcfOK6ynKSELK8jVHm6Rcpf1Odk5mCjoK5nXEVJ4=; b=OJGgyXBcOVBsmz3TwpsVR2u0p74LdRRv27P5VkK5yHvtS0veRXJRbO3uw4iUDgAmpo cR+XR6hHUVBjV04DBpb51tdSILexPsXnwCI2vkJuyj0lnLA3Bhk86FrkjwOQFW7eh0HW PU4TFTKwavSDbAyBbD0YZ5UVQbd5XkWIocv0j7Fmy7MnLoBbVGPssxImtKENJtMezqKk kNCZfKQedhsM+7vAJAk0CodtKqzl9mSqiAPxqN1j4Twlqbshbrbu0RNt8yW6XHE3sD1d KewfW0joPjg0O0EKFdyC/S6t5jxbk8czWzmRpLcPvPCd4KuIrjY0V6oKk7e1jgPHVWbc 5Jzg== X-Gm-Message-State: ALoCoQmPVufmKf9erIQe6L0naI5ulO0h+zkmXBuxCEOyASK3cVx3X7twuqJvS19F2xVsz27c+T9z MIME-Version: 1.0 X-Received: by 10.180.105.129 with SMTP id gm1mr54789462wib.51.1434565557366; Wed, 17 Jun 2015 11:25:57 -0700 (PDT) Received: by 10.27.149.132 with HTTP; Wed, 17 Jun 2015 11:25:57 -0700 (PDT) In-Reply-To: References: Date: Wed, 17 Jun 2015 14:25:57 -0400 Message-ID: Subject: Re: Measuring Samza Job Throughput From: Milinda Pathirage To: dev@samza.apache.org Content-Type: multipart/alternative; boundary=f46d0418262674424d0518bad25a --f46d0418262674424d0518bad25a Content-Type: text/plain; charset=UTF-8 Thank you all for the ideas. I'll have a look at KafkaSystem metrics and SamzaContainerMetrics. Milinda On Wed, Jun 17, 2015 at 2:38 AM, Tao Feng wrote: > Hi, > > One metric I could think of related to Samza job throughput is the > "process-envelop" metric listed in SamzaContainerMetrics. This counter > get incremented whenever the container process meaningful message( > > https://github.com/apache/samza/blob/master/samza-core/src/main/scala/org/apache/samza/container/RunLoop.scala > && > > https://github.com/apache/samza/blob/master/samza-core/src/main/scala/org/apache/samza/container/SamzaContainerMetrics.scala > ). > > But this metric is more like a "QPS" type of metric . > > Thanks, > -Tao > > On Tue, Jun 16, 2015 at 9:11 PM, Milinda Pathirage > wrote: > > > Hi Devs, > > > > I was looking for a way to measure Samza job throughput and found that > its > > possible to do it via Samza's metrics reporter. But there several types > of > > metrics reported via this method. For example, TaskInstanceMetrics > reports > > number of messages sent. But if I wanted to get a measurement like bytes > > per second produced, is there a way to do that. It looks > > like KafkaSystemProducerMetrics and TaskInstanceMetrics only provide > number > > of messages sent. > > > > If any of you have any experience in measuring Samza job throughput, can > > you please share. Really appreciate any ideas on measuring job > throughput. > > > > Thanks > > Milinda > > -- > > Milinda Pathirage > > > > PhD Student | Research Assistant > > School of Informatics and Computing | Data to Insight Center > > Indiana University > > > > twitter: milindalakmal > > skype: milinda.pathirage > > blog: http://milinda.pathirage.org > > > -- Milinda Pathirage PhD Student | Research Assistant School of Informatics and Computing | Data to Insight Center Indiana University twitter: milindalakmal skype: milinda.pathirage blog: http://milinda.pathirage.org --f46d0418262674424d0518bad25a--