Overkill alert. I looked at your test plan, you are testing every piece of static resurce! Just tick the "download embeded resources" in the main SAMPLER if you really really need it. Otherwise avoid it. If you want to know if you have problems with statics, just install YSlow for Firebug and use that to generate a report and suggestion! It makes no sense to test them if your IT ops have installed the proper content delivery infrastructure.
Oh man... I can't believe we still see this in tests. There are so many threads about this. --Adrian S On Thu, Nov 29, 2012 at 5:36 PM, Mitesh Patel <[email protected]>wrote: > Thanks. > > I understand that only samplers get plotted and not controllers. However, > I have 82 samplers (http requests) for my homepage. Some of these samplers > are also used in the About us page, which itself has 60 samplers. So I > potentially have around 100 samplers being plotted, but I have no idea > which request was for which page. > > Thanks, > > > Date: Thu, 29 Nov 2012 17:07:28 +0200 > > Subject: Re: Analysing JMeter results > > From: [email protected] > > To: [email protected] > > > > Hi, > > > > Controllers do not get plotted! Samplers do (its a java thingy, listeners > > wait for info from samplers.) > > > > To view information specific to the whole test I keep a listener as child > > to the thread group or even test plan. But, if I need to view the > specifics > > of a controller, than I add a new listener to the controller (this will > > give me TOTAL that applies to everything from the controller's tree level > > down, in an inclusive manner). > > > > To group samplers you will have to contact the owners and mailing lists > of > > the plugins though. AFAIK it works, but could be wrong and for me, > > listeners in controllers seals the deal: I don't need more. > > > > --Adrian S > > > > On Thu, Nov 29, 2012 at 4:10 PM, Flavio Cysne <[email protected]> > wrote: > > > > > Just modify the script sampler's label (not the URL) to distinct names, > > > like [email protected] and [email protected] > > > > > > > > > 2012/11/29 Mitesh Patel <[email protected]> > > > > > > > Hi, > > > > > > > > I am new to JMeter and have managed to record my first test scenario > via > > > > the proxy. As expected, this records every single request. So, my > plan > > > > looks something like this: > > > > > > > > TEST PLAN > > > > --THREAD GROUP > > > > ----SCENARIO1 (RECORDING CONTROLLER) > > > > ------HOME (TRANSACTION CONTROLLER) > > > > --------home.html (HTTP REQUEST) > > > > --------global.css (HTTP REQUEST) > > > > --------page.js (HTTP REQUEST) > > > > --------banner.png (HTTP REQUEST) > > > > etc > > > > etc > > > > . > > > > . > > > > ------ABOUT US (TRANSACTION CONTROLLER) > > > > --------aboutus.html (HTTP REQUEST) > > > > --------global.css (HTTP REQUEST) > > > > --------aboutus.css (HTTP REQUEST) > > > > --------page.js (HTTP REQUEST) > > > > --------image.png (HTTP REQUEST) > > > > > > > > Now, when I try and plot the results using the OOTB listeners or the > > > > JMETER PLUGINS, I cannot seem to get an accurate view of the results > for > > > > HOME or ABOUT US. It seems to groups similar files i.e. global.css, > > > > page.js. This doesn't really help me analyse the behaviour of the > test. > > > > > > > > Any ideas how I can get around this? > > > > > > > > Thanks, > > > > > > > > >
