jmeter-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sudip Kumar Bhattacharya" <skb.subscripti...@gmail.com>
Subject Re: JMetere JDBC Test Confusing Result
Date Wed, 30 Jun 2010 10:35:26 GMT
You may have to keep the number of threads limited in that case, otherwise it would choke your
db with too many connections and give incorrect results.
Keeping number of threads equal to pool count is a good idea in this case, and avoid jmeter
connection pool.
Sent on my BlackBerry® from Vodafone

-----Original Message-----
From: sebb <sebbaz@gmail.com>
Date: Wed, 30 Jun 2010 11:31:11 
To: JMeter Users List<jmeter-user@jakarta.apache.org>
Reply-To: "JMeter Users List" <jmeter-user@jakarta.apache.org>
Subject: Re: JMetere JDBC Test Confusing Result

On 30/06/2010, jz <jehanzeb.qayyum@gmail.com> wrote:
> Guys its a web applications. And connection pooling will be provided by
>  container. I wanted to test only the time taken by query/stored procedure,
>  not the time of spent in opening connection.

So don't use connection pooling in JMeter.

If you think about it, there will still be the same number of
connections generated.

Either 10 in a pool, or 1 each in 10 threads.

Also, the connections are opened before the samplers run anyway.

>  Regards,
>  Jehanzeb Qayyum
>
>
>
>
>
>  On Wed, Jun 30, 2010 at 3:19 PM, sebb <sebbaz@gmail.com> wrote:
>
>  > On 30/06/2010, Sudip Kumar Bhattacharya <skb.subscriptions@gmail.com>
>  > wrote:
>  > > If it is a j2ee web application, app server wud be doing the connection
>  > pooling.
>  >
>  > Yes, agreed.
>  >
>  > >  If it is a desktop app running from multiple terminals then connection
>  > pooling won't be there across multiple users.
>  >
>  > Yes, agreed.
>  >
>  > >  I hope you are testing for a web application.
>  >
>  > If the OP wants to emulate the behaviour of a web application, then
>  > they need to test using the pooling code actually used by the
>  > applicaton, not the pooling code which happens to be used by JMeter.
>  >
>  > Note that the JMeter pooling implementation cannot be changed (except
>  > by rewriting the code!).
>  >
>  > Alternatively, work out how many independent connections are created
>  > by the web application, and use that many JMeter threads.
>  >
>
> > ---------------------------------------------------------------------
>  > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
>  > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>  >
>  >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org

Mime
View raw message