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 06FE34834 for ; Thu, 19 May 2011 15:37:37 +0000 (UTC) Received: (qmail 91532 invoked by uid 500); 19 May 2011 15:37:36 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 91506 invoked by uid 500); 19 May 2011 15:37:36 -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 91497 invoked by uid 99); 19 May 2011 15:37:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 May 2011 15:37:36 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of will.milspec@gmail.com designates 74.125.82.44 as permitted sender) Received: from [74.125.82.44] (HELO mail-ww0-f44.google.com) (74.125.82.44) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 May 2011 15:37:28 +0000 Received: by wwa36 with SMTP id 36so2090882wwa.13 for ; Thu, 19 May 2011 08:37:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=JRwfHkA8MKQ9lhHfoZEX2FjP/BaIOqa2YsKRn24LvRA=; b=P4iCMZmSDzp4ioHa0fsSydWKlyIuXfz1YoO8B1/W0MNz+937rpb5rvuhXtBMffj477 xN5nGYyDzbOV/+4TQUQQGQIhqwRLLiutopttV7VZthBYosglVa74NjmiYt7RGzqcomZu gXzaF195BBGqxF5vVSXTtwS0TuDKeKqj2OgtQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=cVyK6YrYAPc0pOwe7fOrnKc8JCjOT8jEjvdrS7zBiWC2upILg1FogCPvjbD5y26VKV YB1xKvpLT5RcKQej6WqwgRNGcwpcTlLdQwoI5sXPyaQ/geK7VkGuo+r5NDT22QVTwydS QZp/ThsdsDiWlLFozfzI1USQFkShLpf0coZJw= MIME-Version: 1.0 Received: by 10.216.67.17 with SMTP id i17mr3064846wed.101.1305819427918; Thu, 19 May 2011 08:37:07 -0700 (PDT) Received: by 10.216.12.7 with HTTP; Thu, 19 May 2011 08:37:07 -0700 (PDT) Date: Thu, 19 May 2011 10:37:07 -0500 Message-ID: Subject: Timers, Think Time between requests, and Best Practices From: Will Milspec To: JMeter Users List Content-Type: multipart/alternative; boundary=000e0ce0b49224535704a3a2c701 X-Virus-Checked: Checked by ClamAV on apache.org --000e0ce0b49224535704a3a2c701 Content-Type: text/plain; charset=ISO-8859-1 hi all, My question pertains to use of timers to simulate "think time". Here's a usecase : Use requests two urls: url1 foo.html foo.css foo.js url2 bar.html bar.css bar.js I would like think time to apply only to "main request" (foo.html, bar.html) not the supporting requests (css, js). The reason: the browser downloads these 'supporting' files immediately, not with a 2-5 second delay between .html, .css, and .js I understand from a coworker that: a) if I put a timer at the start of a thread group, according to the following setup, jmeter will randomize the interval between all requests (i.e. including html, css, and .js) b) one must manually edit the script to add timers between foo.html, bar.html ,etc. questions: a) Can someone confirm this b) what's the easiest way to add think time (as described above) to a script? Example setup ThreadGroup HttHeaderManager CSVData Set Config HttpCookieManager GaussianRandomTimer <--- Timer aedded at the start of the thread gropu Transaction Controller SimpleController url1 foo.html foo.css foo.js url2 bar.html bar.css bar.js url3 baz.html baz.css baz.js thanks will --000e0ce0b49224535704a3a2c701--