Return-Path: X-Original-To: apmail-jakarta-jmeter-user-archive@www.apache.org Delivered-To: apmail-jakarta-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 E052562BF for ; Wed, 22 Jun 2011 13:40:07 +0000 (UTC) Received: (qmail 10659 invoked by uid 500); 22 Jun 2011 13:40:07 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 10633 invoked by uid 500); 22 Jun 2011 13:40:07 -0000 Mailing-List: contact jmeter-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "JMeter Users List" Reply-To: "JMeter Users List" Delivered-To: mailing list jmeter-user@jakarta.apache.org Received: (qmail 10624 invoked by uid 99); 22 Jun 2011 13:40:07 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Jun 2011 13:40:07 +0000 X-ASF-Spam-Status: No, hits=4.2 required=5.0 tests=HTML_MESSAGE,SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Jun 2011 13:40:00 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1QZNed-0006U9-CN for jmeter-user@jakarta.apache.org; Wed, 22 Jun 2011 06:39:39 -0700 Date: Wed, 22 Jun 2011 06:39:39 -0700 (PDT) From: jsheth To: jmeter-user@jakarta.apache.org Message-ID: <68A39D9C74BD8241B3659184041D6F6301212519@SRCEXC.srchq.src-solutions.com> In-Reply-To: <4E01F02C.4050707@mpexnet.de> References: <1308700591314-4512401.post@n5.nabble.com> <1308701206781-4512425.post@n5.nabble.com> <68A39D9C74BD8241B3659184041D6F63012124A3@SRCEXC.srchq.src-solutions.com> <68A39D9C74BD8241B3659184041D6F63012124A9@SRCEXC.srchq.src-solutions.com> <68A39D9C74BD8241B3659184041D6F63012124AC@SRCEXC.srchq.src-solutions.com> <4E019F67.3070200@mpexnet.de> <68A39D9C74BD8241B3659184041D6F630121250B@SRCEXC.srchq.src-solutions.com> <4E01F02C.4050707@mpexnet.de> Subject: RE: determining ramp-up period MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_4565_27279087.1308749979378" X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_4565_27279087.1308749979378 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Dear Frank, What is the best way to save results to CSV if I run in silent mode? From: Felix Frank-2 [via JMeter] [mailto:ml-node+4514058-1648290135-45749@n5.nabble.com] Sent: Wednesday, June 22, 2011 9:38 AM To: Jeegnesh Sheth Subject: Re: determining ramp-up period On 06/22/2011 03:30 PM, jsheth wrote: > 2. Aggregate report > > 3. View results tree Deactivating these will most likely help your memory problems. Only enable them if you really need them (i.e. the View Results Tree for debugging, the aggregate report isn't really necessary at any time). A timer interval of 300 ms will be fine in most use cases I can imagine. Cheers, Felix --------------------------------------------------------------------- To unsubscribe, e-mail: [hidden email] For additional commands, e-mail: [hidden email] ________________________________ If you reply to this email, your message will be added to the discussion below: http://jmeter.512774.n5.nabble.com/determining-ramp-up-period-tp4512401p 4514058.html To unsubscribe from determining ramp-up period, click here . -- View this message in context: http://jmeter.512774.n5.nabble.com/determining-ramp-up-period-tp4512401p4514063.html Sent from the JMeter - User mailing list archive at Nabble.com. ------=_Part_4565_27279087.1308749979378--