Return-Path: X-Original-To: apmail-jmeter-dev-archive@minotaur.apache.org Delivered-To: apmail-jmeter-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 4BFAE18AC2 for ; Tue, 30 Jun 2015 22:46:36 +0000 (UTC) Received: (qmail 28902 invoked by uid 500); 30 Jun 2015 22:46:36 -0000 Delivered-To: apmail-jmeter-dev-archive@jmeter.apache.org Received: (qmail 28873 invoked by uid 500); 30 Jun 2015 22:46:36 -0000 Mailing-List: contact dev-help@jmeter.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jmeter.apache.org Delivered-To: mailing list dev@jmeter.apache.org Received: (qmail 28855 invoked by uid 99); 30 Jun 2015 22:46:35 -0000 Received: from Unknown (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jun 2015 22:46:35 +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 34E9ED142D for ; Tue, 30 Jun 2015 22:46:35 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.9 X-Spam-Level: ** X-Spam-Status: No, score=2.9 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-eu-west.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id Jt4lA2pcT01Q for ; Tue, 30 Jun 2015 22:46:24 +0000 (UTC) Received: from mail-ie0-f170.google.com (mail-ie0-f170.google.com [209.85.223.170]) by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with ESMTPS id 7ACAC24C24 for ; Tue, 30 Jun 2015 22:46:23 +0000 (UTC) Received: by iecuq6 with SMTP id uq6so22856555iec.2 for ; Tue, 30 Jun 2015 15:46:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=6T1Irza7Fb+MjvK1D/PID4E5i5rhE/3EjA5eRpuGiTI=; b=m6AxQSsTZfC2FhZRXNHQhSiBfH2XbUmokoJMQYx5iqURwmHaI/9/hT4NkoTV7hLsnf E66WOQVH0ke5V34p447K9CxNBjQzIETydp1KSilj7T/uSLAMdUOHv0t0h7+f4G5Bk2zR ldCsLBJKIkXIvr1p3pXmXjh6uB70Awg/1gFN/FvOtMy82nWMEq8LQJH9Ho0onbg53ocE r881+aLUjUHISziXlzGY08Hs+u7y/4xkJ0oY8bhN1jMNyjrnguKZA1bmVoK521C0Nc+6 OVM3EXbsJysMuAn8nAZCTVHo/+o0cy2G7LSIWg3Yut9xjf07Yo5DricrWjNPrB9qraHf wnWg== MIME-Version: 1.0 X-Received: by 10.43.178.195 with SMTP id ox3mr161082icc.10.1435704382029; Tue, 30 Jun 2015 15:46:22 -0700 (PDT) Received: by 10.107.180.22 with HTTP; Tue, 30 Jun 2015 15:46:21 -0700 (PDT) In-Reply-To: References: Date: Wed, 1 Jul 2015 00:46:21 +0200 Message-ID: Subject: Re: Distributed testing and active threads over time From: Philippe Mouawad To: "dev@jmeter.apache.org" Content-Type: multipart/alternative; boundary=001a11c2c4cab184d10519c3f91c --001a11c2c4cab184d10519c3f91c Content-Type: text/plain; charset=UTF-8 On Wednesday, July 1, 2015, sebb wrote: > On 30 June 2015 at 22:16, Philippe Mouawad > wrote: > > Hello, > > When we do distributed testing and need afterwards to analyze results, we > > need to know how much threads were running at the some point in time by > > doing aggregation work, as illustrated here: > > > > - http://jmeter-plugins.org/wiki/ActiveThreadsOverTime/ > > > > I am just illustrating this need by this particular plugin, but this need > > is here whatever plugin or custom code is used to create this graph. > > > > Currently as each server reports his own number of threads, and this is > > then written to a file, we need a way to know that N number of threads > are > > associated to X server. > > > > I suggest that when a test starts, JMeter client (controller) computes > and > > sends to each server a unique ID, this id would then be stored by the > > server and accessible under a property or function. > > What's wrong with storing the hostname? > > usability and see below > > This way, users would only have to add to their thread group name this > > additional property without any other configuration. > > Already possible; just use the hostname > > Not enough if you have 2 servers on 1 host > > Another better options is to even remove the need for users to add this > > function / property by appending this information automatically from the > > server in the thread name. > > I don't understand what you are proposing here. jmeter client assigns a unique id to each server that the latter uses to name thread and appends to thread group value leading to unique values and possibility to copite the cumulated number of threads among all servers > > > Thoughts ? > > > > > > -- > > Regards. > > Philippe M > -- Cordialement. Philippe Mouawad. --001a11c2c4cab184d10519c3f91c--