jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philip Peake <phi...@vogon.net>
Subject Parallel processing of embeded URLs
Date Mon, 16 Oct 2006 17:26:35 GMT
In any modern browser, the browser normally supports multiple, 
concurrent, HTTP requests (TCP connections).
This is typically used when processing a page requested by the user -- 
embedded links will be processed as they are received, and will be 
processed in parallel up to the maximum concurrent connection limit of 
the browser.

My question is, is it possible to emulate this behavior in Jmeter?

It would appear not. After fetching a page, each of the embedded URLs is 
fetched by the same thread, serially. The reported time for the top 
level page is reported as the sum of the times for loading the top level 
page and each of the embedded URLs. This has no relation at all to the 
time that will be taken by by a browser. the closes seems to be to 
inhibit fetching embeded URLs, but this does not really emulate a real 
world user load where the user will be fetching these URLs.

What is needed is that a thread fetches a page, discovers embedded URLs, 
then spawns up to N more threads to fetch these URLs. The reported time 
should be timed from the commencement of fetching the top level page, to 
the end of the last fetch of an embedded URL. This will correctly 
emulate a browser, and will report times in line with user experience.

Is there any way to do this?

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org


Mime
View raw message