Benefits of using connection pooling

Benefits of using connection pooling

Postby Simon C » Wed 24 Mar 2010 14:31

What are the performance benefits of using connection pooling (in terms of time to actually set up a connection), and what are the differences between devart connection pooling and oci connection pooling? Are there situations where you should one or the other, or disable pooling completely?
Simon C
 
Posts: 11
Joined: Mon 14 Dec 2009 16:33

Postby StanislavK » Wed 24 Mar 2010 16:51

Provided that the connection was once opened and placed to the pool, it can be reopened much faster. For details, please see the MSDN documentation:
http://msdn.microsoft.com/en-us/library/bb399543.aspx
http://msdn.microsoft.com/en-us/library/ms254502.aspx

The OCI pool is controlled by the Oracle client and is used for OCI connections. dotConnect for Oracle provides its own connection pool which is used for Direct connections.

If connection pooling is enabled, the connection is not actually closed when you call the Close() method in your application. If you need to have full control on your connections, you may be interested in disabling the pooling feature.
StanislavK
Devart Team
 
Posts: 1710
Joined: Thu 03 Dec 2009 10:48

Postby Alladin » Mon 19 Apr 2010 15:27

What's a reason of using Devart connection pooling where there is a native one?

For direct mode only?
Alladin
 
Posts: 149
Joined: Mon 27 Nov 2006 16:18

Postby StanislavK » Wed 21 Apr 2010 09:57

The connection pooling feature was implemented for the Direct mode. In the OCI mode, you may use either our or native pooling without considerable differences in performance.
StanislavK
Devart Team
 
Posts: 1710
Joined: Thu 03 Dec 2009 10:48


Return to dotConnect for Oracle