jmeter-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <>
Subject Re: Issues 52673 / 52698 / 41545 / 52707 / 52502
Date Wed, 21 Mar 2012 01:11:54 GMT
On 20 March 2012 20:29, Geoff Simmons <> wrote:
> Hash: SHA256
> On 3/20/12 8:09 PM, Shmuel Krakower wrote:
>> One other thing I find problematic is that you cannot change the
>> created load. I.e. if you want to see how the system will handle
>> twice of the current load.. but I guess you can work around this..
> There are a number of things you could do, such as make additional
> copies of the request logs, and change the intervals between requests
> in the logs. Then you'd have to make sure that the results do not
> create some sort of error, for example by duplicating DB updates, or
> something like that. This all runs afoul of the idea of reproducing
> recorded traffic, but the sampler doesn't know or care where the
> request logs came from or how they were built.
>> Regarding your thoughts of allowing utilization of JMeter config
>> elements like cookies, I guess that another approach (which maybe
>> others already implemented?) will be to simply convert apache logs
>> into jmeter samplers(creating a jmx file) but I am not sure how
>> jmeter will handle thousands of samplers in one script.
> As sebb mentioned, that's the Access Log Samper (just the one sampler
> is enough). As I mentioned earlier, access logs mean that you are
> limited to GET requests and any headers the access log contains, and
> you have to estimate the concurrency of the logged requests.

I meant that the Access Log sampler could be extended to parse other
logs which have sufficient info to recreate requests other than just

>> Anyway, this is interesting topic.. maybe more related to the users
>> list and not dev...
> We can take it over there, it just came up on dev because we've
> offered the sampler for JMeter, and the question was how generally
> useful it would be.
> - From the feedback so far, I'm thinking we should bring it up again at
> a later time, when we have stronger tool support for obtaining the
> request logs, and easier ways of solving problems with sessions and
> the like, as we've been discussing today. Sound about right?
> Best,
> Geoff
> - --
> UPLEX Systemoptimierung
> Schwanenwik 24
> 22087 Hamburg
> Mob: +49-176-63690917
> Version: GnuPG/MacGPG2 v2.0.14 (Darwin)
> Comment: Using GnuPG with Mozilla -
> M9SetlBcNqkMmV/HgzQKVHTB+GBqX/d0GREdjHV4bFM8/OuB5uTF7fAshxMOece6
> +/ep6QmKY/LNLnNBgLeOH5NzU8Q4EDLxePf0ei3Lx0HOZRPnkSJc85dStsIUb3pq
> pYP4LOjLhkdeVkOy9K5z4cWe402hmzW2AcSfnV6Z4G2DbO1CQXBZNSjV+Cv3juBN
> IZEEDMyjkR2/OOcZdW+iTMFJiSRqT5AwoOnr7uQQ7ewd+QBoGdtRE9FI3KxVN4iD
> WlACCVwqg+qBCyTOAVIjH+4Rs4H9AzF2bljhnVzGAGyf057/jwu44NgujoWPV4w3
> 75ZG18aRvCffZ5jaIv4u9HEKKyFtXgfgGkLtH4zKKCOGcW1hVdTY9dqB3fKg7EJh
> Zgss6WJi2gp9Z+1gJp86NGzn0YzA+KB4r+bwtSbLXcDbNUuicogyg/NAjR808Zt7
> KdG+0zXYkIMU6hWX9b0qy8f9OO+KbUzuvt4OivIFHPjvzfItpURTMZCdkCn5m+Wp
> czg+tNGN6ST7U3LkgRC6AhKXRc7Q1ZQgqpiNh2mvGIvjUhj5CA6jLhFDvUSGAOID
> SrKO+9XYl5es/M/fHDqPoF/d1J7SatUOCOYTnFy0p1PCFFJLP0qbhEYnqjd+HVoh
> XvTTV5Wz7Mts+IF0uX7K
> =J2op

View raw message