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 11CD36A93 for ; Mon, 13 Jun 2011 22:25:49 +0000 (UTC) Received: (qmail 17700 invoked by uid 500); 13 Jun 2011 22:25:48 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 17674 invoked by uid 500); 13 Jun 2011 22:25:48 -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 17665 invoked by uid 99); 13 Jun 2011 22:25:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Jun 2011 22:25:48 +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 flyingrhenquest@gmail.com designates 209.85.213.172 as permitted sender) Received: from [209.85.213.172] (HELO mail-yx0-f172.google.com) (209.85.213.172) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 Jun 2011 22:25:40 +0000 Received: by yxt33 with SMTP id 33so1049790yxt.31 for ; Mon, 13 Jun 2011 15:25:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=PbMhEmXbxT5H6Ol+C1zzAmQThDQLnW+i8nmeG6b7D4Q=; b=uoyxtYvzg5sO9WV56Flc2tM0JSWI1AizZqqfpk1OumeDTRufoimYidqSBT3AdvqUHt f3pkcQK7Ug/gTITCPS9Ny4eJwLNiUxuw99N7AU9BREIy7OdZuOcA8yWwb7b2AHfRg90U 83hoNZo+NHXOTGttBgrTtfYXJbs/xO/Db+PFQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=KAWyUvBlMH7ne7hR6snaZCNTgymaPy2DiyEXLBvLD7bWU9tpLKbHl8hVfrXVA7rEek 47Qy++ctuTCHCO7sgitoim4za033K55FJ++U8ynGHha2A/3WZ6WSwqoAzT5JTH695D/o 03HO+rI5/jjoHusi8ikbdkelvzGrGuNjhoLLs= MIME-Version: 1.0 Received: by 10.150.13.17 with SMTP id 17mr6729176ybm.394.1308003919732; Mon, 13 Jun 2011 15:25:19 -0700 (PDT) Received: by 10.150.147.19 with HTTP; Mon, 13 Jun 2011 15:25:19 -0700 (PDT) In-Reply-To: References: <1307918834312-4482737.post@n5.nabble.com> Date: Mon, 13 Jun 2011 16:25:19 -0600 Message-ID: Subject: Re: Concurrent HTTP requests to simulate AJAX client From: Bruce Ide To: JMeter Users List Content-Type: multipart/alternative; boundary=000e0cd7622e00214304a59f6557 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd7622e00214304a59f6557 Content-Type: text/plain; charset=ISO-8859-1 You'd determine which tiles you wanted to request in advance, and you'd put that information in a CSV file. Then you'd write a test that requests a tile using information from the CSV data set. When you ramp up the number of users (running threads) in your thread group, the CSV data set would parcel your requests out equally among all threads. It does this one line at a time in the file, thread 1 gets the first line, thread 2 gets the second line, and so forth. As long as you build your CSV files to access adjacent tiles, it should look like a user with a browser to the application. You could even maintain different datasets to simulate light or heavy usage. -- Bruce Ide FlyingRhenquest@gmail.com --000e0cd7622e00214304a59f6557--