While this is not usually an issue with the quick connection setup that MySQL offers compared to other databases, creating connections still has networking and JDBC driver overhead that will be avoided if connections are “recycled.”

Simplified programming model:

When using connection pooling, each individual thread can act as though it has created its own JDBC connection, allowing you to use straight-forward JDBC programming techniques.

Controlled resource usage:

If you don’t use connection pooling, and instead create a new connection every time a thread needs one, your application’s resource usage can be quite wasteful and lead to unpredictable behavior under load.
Remember that each connection to MySQL has overhead (memory, CPU, context switches, etc) on both the client and server side. Every connection limits how many resources there are available to your application as well as the MySQL server. Many of these resources will be used whether or not the connection is actually doing any useful work!
Connection pools can be tuned to maximize performance, while keeping resource utilization below the point where your application will start to fail rather than just run slower.

Random Posts

• March 25, 2009 -- Creating a Stateful session Bean (1)
• February 15, 2009 -- Providing current date and time using Stateless session bean (0)
• September 22, 2008 -- What is Default Package in Java (0)
• January 26, 2009 -- File Uploading Using Servlet (0)
• September 2, 2008 -- Define Session (0)