Return-Path: X-Original-To: apmail-jmeter-user-archive@www.apache.org Delivered-To: apmail-jmeter-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9582AF317 for ; Wed, 27 Mar 2013 20:03:23 +0000 (UTC) Received: (qmail 19582 invoked by uid 500); 27 Mar 2013 20:03:23 -0000 Delivered-To: apmail-jmeter-user-archive@jmeter.apache.org Received: (qmail 19555 invoked by uid 500); 27 Mar 2013 20:03:22 -0000 Mailing-List: contact user-help@jmeter.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "JMeter Users List" Delivered-To: mailing list user@jmeter.apache.org Received: (qmail 19546 invoked by uid 99); 27 Mar 2013 20:03:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Mar 2013 20:03:22 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sebbaz@gmail.com designates 209.85.212.182 as permitted sender) Received: from [209.85.212.182] (HELO mail-wi0-f182.google.com) (209.85.212.182) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 Mar 2013 20:03:16 +0000 Received: by mail-wi0-f182.google.com with SMTP id hi18so2607416wib.9 for ; Wed, 27 Mar 2013 13:02:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=mEEc85yz44ftxoR9gD1Xg3t1MkBVsneop3XdUr35ug4=; b=zBBxDFOlawYvncqWmBVO/qdfHxwmadnptSj6agzo2/t1C46xgh8572JT+4FJP5rsQM hRAdxYhRTv18TlX0MEGg6GOUljqY/OIXlisNT6C1bM47DLlrn0+33g6KfmAX9fh35MFV 5yLTjh9RhpHPLcfj2A/G71FXna57yaMy/HgXczizvitr1+/q2H+2ojtLkDmaYKOH7UtJ qJu29c2J8h4iYPFCskIEptr5n5IDpBzhZms/33tg2Hai8XP3F1boNbqJ2EXkMEDkGNBR vrMC/H6YIVKipCcPJapv36uKMvHk4l8Q5aCdAr4j5GGpXwz0WP6DT6nxxSeP1dcAVojG RpyA== MIME-Version: 1.0 X-Received: by 10.180.78.168 with SMTP id c8mr11926419wix.27.1364414576490; Wed, 27 Mar 2013 13:02:56 -0700 (PDT) Received: by 10.194.243.10 with HTTP; Wed, 27 Mar 2013 13:02:56 -0700 (PDT) In-Reply-To: References: <5152AAF6.4060106@iiitb.net> <5152B4F0.1000705@iiitb.net> Date: Wed, 27 Mar 2013 20:02:56 +0000 Message-ID: Subject: Re: Not able to log "throughput" in a log file From: sebb To: JMeter Users List Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org On 27 March 2013 19:47, Flavio Cysne wrote: >> This is becaused it is measured to the end of the first read from the > response. > > I always thought that latency should be the amount of time between the > request sent and the first byte received, not the first read of an entire > packet. Ideally, yes, but it's not easy/possible to do that. > I've seen some cases, using JMeter 2.7, that latency is greater than > elapsed time. How much greater? > I'll try to reproduce this issue and raise a bug report ASAP. > I'll also try it on JMeter 2.9. > Thanks sebb --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscribe@jmeter.apache.org For additional commands, e-mail: user-help@jmeter.apache.org