To pool or not to pool

  • Thread starter Thread starter Shimon Sim
  • Start date Start date
S

Shimon Sim

The question is should I use the connection pooling.
Here are the details.
I am developing ASP.NET application it is running for some time already
while we keep adding some features. Recently noticed that some pages return
error - the amount of connection exceeded the maximum amount.
I started looking at the amount of connections my application using. I
created simple path that is using few pages. One of these pages has have
search functionality.
Performance monitor stopped at 33 - connections - this is one user?!! No
wonder that application reached max amount.

I am using DAAB 1.0. I keep my connection string in config file and load it
into static variable to increase performance. So I assume that I should use
pool just fine. But for some reason connections don't want to recycle.

I removed pooling and I had just in one place for a second amount of
connection 14 all other time it was 1-3.
So should I pool or not? Or may be I missed something?
Thanks
Shimon.
 
I am using DAAB 1.0. I keep my connection string in config file and load
it into static variable to increase performance. So I assume that I should
use pool just fine. But for some reason connections don't want to recycle.

Are you certain you are closing connections as soon as they're no longer
required?
 
Back
Top