Re: Manually Search result is returning in 30sec but jmeter in mili-sec

[Deepak Shetty <sh...@gmail.com>]

a. is your test correct. Did you verify the results being returned(using
View results tree) for a sample run? do you have assertions that verify
correctness? JMeter will only flag an error , by default for HTTP errors ,
it wont be able to detect application errors unless you tell it what to do
b. Does your load runner test download all embedded resources (e.g.
JS/CSS/Images). Does your Jmeter test do the same

regards
deepak

On Fri, Jan 15, 2010 at 3:21 PM, bh41637 <bh...@yahoo.com> wrote:

>
> I have a ThreadGroup for my app SiteWide Search. I think I recorded the
> functionality just fine with HTTP Proxy but the response time I am
> getting only in mili-sec but in reality it is about avg 30sec. Did
> you encounter this same issue while doing the same script? I did the same
> in
> LoadRunner and the result looks correct. Why Jmeter is returning the result
> so quickly? Any idea?
>
> --
> View this message in context:
> http://old.nabble.com/Manually-Search-result-is-returning-in-30sec-but-jmeter-in-mili-sec-tp27184998p27184998.html
> Sent from the JMeter - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>