On 05/09/2009, Bruce Foster <[email protected]> wrote: > Hi Deepak and others, > > Thanks for quick response and help. > > Yes, the listener Save_Responses_to_a_file did the trick for me. Just > ran a test with 1000 request to see the response and got all the > images saved in directory. Well, the purpose was to check the response > and not the performance (response time). After making sure that the > image are correct, I ran the actual test to get the performance > results. > > Well, I'm using the random function and it worked well to generate > random bound box request. Also, I adapted the osgeo test method of > using pre generated csv file. > > got a good result of 12 user per second in one method for total > random, and 20 users per second for 800x600px random bbox request. > need further more to test. > > now i have to find out how to log the 10000 request time. jmeter gives > only summary/average.
In the GUI, that depends on the Listener - e.g. the Table View Listener shows response times. But don't use this for a performance test as it will use lots of memory. Just save the responses to a file, and you have all the details there, depending on what you have configured. Probably easiest to use CSV output. > Cheers > > bruce. > > > > > > On Thu, Sep 3, 2009 at 7:16 PM, sebb<[email protected]> wrote: > > On 03/09/2009, Adrian Speteanu <[email protected]> wrote: > >> 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. > > > > Not necessarily; the server may degrade under load. > > > > For checking responses such as images, consider using > > > > > http://jakarta.apache.org/jmeter/usermanual/component_reference.html#MD5Hex_Assertion > > > > Or you can use the HTTP sampler option "Save response as MD5 hash?" > > and check that. > > > >> 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] > >> > >> > > > > --------------------------------------------------------------------- > > 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
