tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ahmed Abbas" <aelga...@asset.com.eg>
Subject RE: failure notice
Date Mon, 24 Nov 2008 16:01:13 GMT
Dear,

I didn't create a connection pool of one connection. The configuration of the datasource in
the first case was as follows:
<Context path="/FamilyHandlerOpt">
  <Resource name="jdbc/VAS_FAF" auth="Container" type="oracle.jdbc.pool.OracleDataSource"
driverClassName="oracle.jdbc.OracleDriver" factory="oracle.jdbc.pool.OracleDataSourceFactory"
url="jdbc:oracle:thin:@172.21.201.60:1521:FMLYPRD1" username="family2" password="family2"
maxActive="100" maxIdle="10" maxWait="-1" /> 
  </Context>

In the second case, I opened the connections using the same configuration of the datasource
above, kept the connections alive and pooled the threads on these connections.
The response time of the second case was improved dramatically and the system scalability
was achieved.

Best regards,
Ahmed Abbas

-----Original Message-----
From: Christopher Schultz [mailto:chris@christopherschultz.net] 
Sent: Friday, November 14, 2008 6:40 PM
To: Tomcat Users List
Subject: Re: failure notice

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

To whom it may concern,

aelgamal , wrote:
> The above scenario resulted in very poor scalability during the stress
> testing. When the average response time for 1 thread was x msec, the average
> response time for 2 threads was 2x and 3 threads was 3x and so on.

How did you configure your data source?

> When I created a pool of connections (15 connections) in the Servlet and
> kept the connections of this pool alive the scalability improved. The
> average response time for a 150 concurrent threads was slightly higher than
> the average response time for 1 thread.

How did you configure your data source, here?

> Please advice why the poor performance when I used tomcat data source.

Tomcat can be configured to use a data source with a connection pool
size of 1. It's silly, but possible. If this is what you did, then you
simply weren't pooling connections and you should expect that pooling
would certainly improve performance.

If you're interested in playing with connection pools, help out Filip by
using his new Tomcat connection pool he's testing. I'm sure he'd love
the feedback.

- -chris

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkkdqfwACgkQ9CaO5/Lv0PBXdACgjq/4JJZKJ+DgNn64szioNSZl
mvgAoMN8Qb9oPjizMzzeXyGJQn6IPQmO
=7ATP
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message