true, you can use either method for what you said you need, but in
this case, saving the file on the test machine will significantly
increase the stress on the test environment (quality image files mean
lots of space and that means disk usage).

if you run the test with fewer requests and see that you get the
responses you expect, then you will also get these responses in a load
/ stress test even if you don't save the files locally. this is
recommended.

On Tue, Sep 1, 2009 at 2:04 AM, Deepak Shetty<[email protected]> wrote:
> Hi
> you can add
> http://jakarta.apache.org/jmeter/usermanual/component_reference.html#Save_Responses_to_a_file
> OR you can add a BeanShell Post Assertion  that can read the bytes and save
> it to whatever you want or run comparisons
> OR
> http://jakarta.apache.org/jmeter/usermanual/component_reference.html#Sample_Result_Save_Configuration
> (Check Save Response Data) - I wouldnt do this though because some binary
> can cause the xml to break
>
>
> regards
> deepak
>
> On Mon, Aug 31, 2009 at 3:57 PM, Bruce Foster <[email protected]> wrote:
>
>> Hi List,
>>
>> I'm totally new to jmeter and also benchmarking.
>>
>> I'm testing a WMS (web map service) service performance of three
>> server softwares. Basically, they are GET request of images from a
>> server.
>>
>> Is there a way to SAVE the requested images? I have the mandate to
>> make sure that the response from the servers are exactly the same
>> image (in resolution, quality) that we request for.
>>
>> When I did a test, I put a network monitor. I could see 70mb of data
>> is transfered. Now, where to look for that, does jmeter save them in
>> cache?
>>
>> Note, I'm doing everything on a vmware machine running on my notebook.
>>
>>
>> Thanks
>> Bruce
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to