Thank you for your reply. Sure. I will keep Flood IO separate from this thread/group.
To your point above, yes I am adding 1 common response assertion for all HTTP requests. But this is used to ignore response codes for sub samples. Some third party JS, CSS responses in errors like 304, 302. Is this not a good practice to use response assertion for all http req? I also used response assertion for text verification such as "thank you for your order". That's it. thanks again. On Sat, Oct 10, 2015 at 12:20 PM, Milamber <[email protected]> wrote: > > Perhaps, this mailing list isn't the best place to debug Flood.io service. > > Have you in your JMeter script add some assertion response on the page to > check the return data? > > On 10/10/2015 01:46, Ankit Sethiya wrote: > >> Hello, >> >> I am running JMeter test using a third party service called Floo.IO (this >> is similar to blazemeter) which allows me to execute my JMeter scripts on >> cloud from different locations. >> >> Now, my question is: >> >> I ran a test for about an hour.. and at 20 to 30 mins in the test i >> noticed >> that site was extremely slow in my browser for example homepage was taking >> 30+ secs to load however in my flood.io report it was still showing as >> 1.5 >> secs. Same for each page. What could possibly be the reason for that? >> >> I did select "clear cookies and cache after each iteration (in JMeter)". >> (Am I not suppose to do it?) >> I did select forever loop for each thread and ramped up 300 concurrent >> users in 3 mins. >> I gave timers between each requests. >> >> Here is my flood.io report if that helps understanding my question - >> https://flood.io/9UNmaSBMkNhBvZGfGuwAEw >> >> Thank you very much in advance. >> >> >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Software Quality Analyst Los Angeles, CA 626.202.5415
