Return-Path: Delivered-To: apmail-jakarta-jmeter-user-archive@www.apache.org Received: (qmail 65250 invoked from network); 10 Sep 2010 18:33:42 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 10 Sep 2010 18:33:42 -0000 Received: (qmail 36035 invoked by uid 500); 10 Sep 2010 18:33:41 -0000 Delivered-To: apmail-jakarta-jmeter-user-archive@jakarta.apache.org Received: (qmail 35942 invoked by uid 500); 10 Sep 2010 18:33:41 -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 35934 invoked by uid 99); 10 Sep 2010 18:33:40 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Sep 2010 18:33:40 +0000 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=FREEMAIL_FROM,SPF_HELO_PASS,SPF_NEUTRAL,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: 216.139.236.158 is neither permitted nor denied by domain of strodion@gmail.com) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Sep 2010 18:33:36 +0000 Received: from sam.nabble.com ([192.168.236.26]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1Ou8PT-0002vk-Lz for jmeter-user@jakarta.apache.org; Fri, 10 Sep 2010 11:33:15 -0700 Date: Fri, 10 Sep 2010 11:33:15 -0700 (PDT) From: Prostak To: jmeter-user@jakarta.apache.org Message-ID: <1284143595676-2835419.post@n5.nabble.com> In-Reply-To: References: <1283985522003-2826174.post@n5.nabble.com> <4C8886D1.6010700@mpexnet.de> <1284052416329-2828327.post@n5.nabble.com> <1284055258464-2831982.post@n5.nabble.com> <1284062978811-2834078.post@n5.nabble.com> <1284075093708-2834285.post@n5.nabble.com> Subject: Re: Test plan for (970 page requests every 5 min) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit >Ah I didn't notice your original table separated out pages from requests. >whereas I used the terms interchangeably. >So for this mail a Page = the URL the browser requests. Resources = Embedded >Javascript/CSS/Images that the browser automatically requests >I generally tend not to test out anything related to >CSS/Javascript/Image(unless Im stressing the webserver) while doing any >response time testing so while a Page may include 50 resources I would only >figure out values for the page. If I exclude all resources then it wouldn't reflect the true new user. I also have noticed, that when recording through proxy on Jmeter, it records resources only once (for instance when loading the home page I get all css files, icons and general images). When I browse through tabs, it doesn't rerecord all the resources. Only the unique resources of some pages. I think such recording reflects the true unique user. Therefore when I stop recording and add wait times, it would give me a realistic unique user, which then I can multiply (increase number of threads), to receive the realistic load. Don't you agree? .......... now when I reread it, I suspect that this question relates to the question about concurrent users at the near end of this message. >If you are using firebug then you should be using the network tab and >looking at the times there. A javascript/DHTML heavy app may take more time >to load but Jmeter cant capture this. I was going to ask you next if Jmeter can give me a total load time for each page, but then I found your answer to another guy on similar question (http://www.mail-archive.com/jmeter-user@jakarta.apache.org/msg28618.html). It is disappointing. I understand that there are a lot of factors (browser, network, returning user, users machine), but it would be nice to have that data at least for your specific factors. So it would be nice to have page load time for FF 3.6, WinXP, network such and such, 20 concurrent users... Too bad to hear that Jmeter can't do it. >A browser can reuse sockets (keep alive - but we'll ignore that for now ). >In any case its the number of concurrent connections that usually cause >problems. So if a browser makes a request for a page and then finds out the >page has 50 resources it will use anything from 2 to N concurrent >connections(It used to be that the browser would only make 2 connections per >domain but I think more recent browsers have increased this value , I dont >know the value of N) . JMeter on the other hand does no such thing. Can you please explain here a little more? Let's say each Jmeter thread contains 50 requests (all pages and all resources combined): Does Jmeter establish 50 concurrent connections? Or does it establish only one concurrent connection for the whole thread? > you check the download embedded resources checkbox Sorry, didn't understand. Do you mean "Retrieve All Embedded Resources from HTML Files" in HTTP Proxy server? If not, which one you mean? Thanks, Prostak -- View this message in context: http://jmeter.512774.n5.nabble.com/Test-plan-for-970-page-requests-every-5-min-tp2826174p2835419.html Sent from the JMeter - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: jmeter-user-help@jakarta.apache.org