To give you more idea. Here are current settings: Test Plan -----JDBC Connection Config -----Thread Group 1 ----------JDBC Request 1 -----Thread Group 2 ----------JDBC Request 2 -----View Result in Table
Here both JDBC Requests are using same connection pool. Regards, Jehanzeb Qayyum On Wed, Jun 30, 2010 at 3:42 PM, jz <[email protected]> wrote: > Results do not agree with your proposition. > For Thread group 1 average sample time was 2000 ms > and for thread group 2 average sample time 250 ms > > > > > Regards, > Jehanzeb Qayyum > > > > > > On Wed, Jun 30, 2010 at 3:31 PM, sebb <[email protected]> wrote: > >> On 30/06/2010, jz <[email protected]> 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 <[email protected]> wrote: >> > >> > > On 30/06/2010, Sudip Kumar Bhattacharya <[email protected] >> > >> > > 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: [email protected] >> > > For additional commands, e-mail: [email protected] >> > > >> > > >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >
