You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Noel O'Brien <no...@newbay.com> on 2009/04/21 16:41:40 UTC
Replace JDBC Pool
Hi All,
I'm seeing some issues with slow INSERT/COMMIT times (about 4sec!) to MySQL
from our product and would like to recreate the same setup with JMeter to rule
out certain components (hibernate, DBCP, etc.)
Our product uses DBCP for connection pooling but JMeter uses Avalon if I'm not
mistaken. Is it an easy task to replace Avalon with DBCP in JMeter?
Regards,
Noel
Re: Replace JDBC Pool
Posted by sebb <se...@gmail.com>.
On 21/04/2009, Noel O'Brien <no...@newbay.com> wrote:
>
>
>
> On Tuesday 21 April 2009 15:47:16 sebb wrote:
>
> > On 21/04/2009, Noel O'Brien <no...@newbay.com> wrote:
>
> > > Hi All,
>
> > >
>
> > > I'm seeing some issues with slow INSERT/COMMIT times (about 4sec!) to
>
> > > MySQL from our product and would like to recreate the same setup with
>
> > > JMeter to rule out certain components (hibernate, DBCP, etc.)
>
> > >
>
> > > Our product uses DBCP for connection pooling but JMeter uses Avalon if
>
> > > I'm not mistaken. Is it an easy task to replace Avalon with DBCP in
>
> > > JMeter?
>
> >
>
> > No, but if you set the JDBC Config Max Number of Connections to 0, it
>
> > will use a connection per thread, i.e. no pooling.
>
>
>
> Interesting, I'll try this to see what the effect is.
>
>
>
> > I'd like to remove connection pooling altogether from JMeter.
>
> > JMeter threads are supposed to be independent users, and users don't
>
> > share DB pools.
>
>
>
> That's a shame, as it pooling was useful in my case to simulate how our
> product works and to help point towards the DB as a bottleneck.
The only way to test that is to use exactly the same pool and settings
as the application, which may not be possible in the general case.
However, you can still simulate your application - as far as the
server is concerned it still just sees JDBC connections and queries.
You just have to know what load your application presents on the
server-side of the pool.
> I can see
> your point thought, from an end-user point of view there's no sharing of DB
> pools. Maybe it could be left an an option?
>
It is currently still an option.
>
> > > Regards,
>
> > >
>
> > > Noel
>
> >
>
> >
> ---------------------------------------------------------------------
>
> > 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
Re: Replace JDBC Pool
Posted by Noel O'Brien <no...@newbay.com>.
On Tuesday 21 April 2009 15:47:16 sebb wrote:
> On 21/04/2009, Noel O'Brien <no...@newbay.com> wrote:
> > Hi All,
> >
> > I'm seeing some issues with slow INSERT/COMMIT times (about 4sec!) to
> > MySQL from our product and would like to recreate the same setup with
> > JMeter to rule out certain components (hibernate, DBCP, etc.)
> >
> > Our product uses DBCP for connection pooling but JMeter uses Avalon if
> > I'm not mistaken. Is it an easy task to replace Avalon with DBCP in
> > JMeter?
>
> No, but if you set the JDBC Config Max Number of Connections to 0, it
> will use a connection per thread, i.e. no pooling.
Interesting, I'll try this to see what the effect is.
> I'd like to remove connection pooling altogether from JMeter.
> JMeter threads are supposed to be independent users, and users don't
> share DB pools.
That's a shame, as it pooling was useful in my case to simulate how our
product works and to help point towards the DB as a bottleneck. I can see your
point thought, from an end-user point of view there's no sharing of DB pools.
Maybe it could be left an an option?
> > Regards,
> >
> > Noel
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Replace JDBC Pool
Posted by sebb <se...@gmail.com>.
On 21/04/2009, Noel O'Brien <no...@newbay.com> wrote:
> Hi All,
>
> I'm seeing some issues with slow INSERT/COMMIT times (about 4sec!) to MySQL
> from our product and would like to recreate the same setup with JMeter to rule
> out certain components (hibernate, DBCP, etc.)
>
> Our product uses DBCP for connection pooling but JMeter uses Avalon if I'm not
> mistaken. Is it an easy task to replace Avalon with DBCP in JMeter?
No, but if you set the JDBC Config Max Number of Connections to 0, it
will use a connection per thread, i.e. no pooling.
I'd like to remove connection pooling altogether from JMeter.
JMeter threads are supposed to be independent users, and users don't
share DB pools.
> Regards,
>
> Noel
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org