-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
jonathan.chiu@stripped wrote:
> AFAIK, creation of connection from DB is expensive. This is one of the
> reasons why we need connection pooling.
>
Jonathan,
While that might be true for other databases, it's not true for MySQL
(connections are a few ms. to create).
The real reason to use connection pooling is as a resource limiter so
that you do not waste MySQL server-side resources for threads that are
effectively doing nothing.
Haitao's issue might be due to some locking in the database server, thus
effectively serializing his four connections, or he might not be
actually producing enough load to actually be able to measure any
difference between his two approaches. If he could post his DDL, the
relative size(s) of his data set(s) and the queries, that would be
somewhere to start.
-Mark
- --
Mr. Mark Matthews
MySQL AB, Software Development Manager, J2EE and Windows Platforms
Office: +1 708 332 0507
www.mysql.com
MySQL Guide to Lower TCO
http://www.mysql.com/it-resources/white-papers/tco.php
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFAxRgLtvXNTca6JD8RAjiSAJ0R5b6MNW0SdY5z4eJtmfgAV0ZMtgCgtGyn
037apgXT972UAR3Khkg7ITI=
=4bja
-----END PGP SIGNATURE-----
