Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

ado.net connection pooling question

Posted on 2011-03-21
9
Medium Priority
?
322 Views
Last Modified: 2012-06-27
I'm trying to understand connection pooling as it relates to a multi-threaded application.
If I have 5 threads continuously running and they all create a sql connection, shouldn't I have 5 distinct connections to the db?  Using the sql trace I don't see but 2.

If I up my threads to 10 the connection count doesn't change.  Inside the thread, the connection is opened and closed as it is used.

I understand the connection pooling just returns it back to the pool but I would still think I would have more than 2 connections at any given time. The threads run very quickly but upping the thread count doesn't seem to improve performance.

Rut
0
Comment
Question by:rutledgj
  • 5
  • 4
9 Comments
 
LVL 13

Expert Comment

by:gamarrojgq
ID: 35184419
Hi,

Connection pooling is a useful way to reuse connections for multiple requests, rather than paying the overhead of opening and closing a connection for each request. It's done implicitly, but you get one pool per unique connection string. If you're generating connection strings dynamically, make sure the strings are identical each time so pooling occurs.

Hope that helps
0
 

Author Comment

by:rutledgj
ID: 35185549
So are you saying that one connection created can result in multiple connections through connection pooling?
0
 
LVL 13

Expert Comment

by:gamarrojgq
ID: 35185614
Well, connection pooling use active connections of the pool for consecutive requests, rather than creating a new connection each time.

So if your threads have the same  Connection String, the first one will Create and Open a DB Connection and the second, third, etc will use the same connection instead of create another a new one.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 

Author Comment

by:rutledgj
ID: 35185772
so the second (and subsequent) threads will have to wait until the first thread finishes with the connection until it can use it? The connection it a single object created as a public shared variable.
0
 
LVL 13

Expert Comment

by:gamarrojgq
ID: 35186044
Ok, the connection pool will work this way when a thread needs a DB Connection:

If any unused connection is available, it returns one.

If all connections are used up, a new connection is created and added to the pool.

If the number of connections reaches the maximum number of connections in the pool, the requests are queued until a connection becomes free for reuse.

So, the second and subsequent threads will have to wait ONLY if the connection created by the First Thread is still in use, if not, they will use it rigth away
0
 

Author Comment

by:rutledgj
ID: 35188757
I guess this is what doesn't make sense in your statement.

If any unused connection is available, it returns one.

If all connections are used up, a new connection is created and added to the pool.

If my application opens one connection for all threads to use and thread #1 is using it, does the connection pool create more connections for the remaining threads or do they have to wait for thread #1 to finish?
0
 
LVL 13

Accepted Solution

by:
gamarrojgq earned 1000 total points
ID: 35189227
ok, that would depend on the pool maxpoolsize property, if you set this property > 1, if the Thread #1 is using the connection, the connection pool will create another connection for the memaining threads, but if you are not using connection pool or the maxpoolsize = 1, then the other threads will have to wait

Example

Thread 1 Request a DB Connection    
       The connection Pool Creates a New One
Thread 1 Use it and Close it

Thread 2 Request a DB Connection
       The connection Pool reuse the connection Created by Thread1
Thread 2 START using the connection

Thread 3 Request a DB Connectino
       Since the Thread 2 is still using the connection Created by Thread1 it Creates a Second
Thread 3 Use the new Connection an Close It

Thread 2 Close the connection Created by Thread1

And this cycle repeats according to the Threads DB Connections requests



0
 

Author Closing Comment

by:rutledgj
ID: 35189425
Thanks. Just one comment. Isn't connection pooling used by default in ado.net? Didn't know you had to turn it on.
0
 
LVL 13

Expert Comment

by:gamarrojgq
ID: 35190133
Yes, it is on by default, but you can turn it off if you want.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Microsoft Reports are based on a report definition, which is an XML file that describes data and layout for the report, with a different extension. You can create a client-side report definition language (*.rdlc) file with Visual Studio, and build g…
It was really hard time for me to get the understanding of Delegates in C#. I went through many websites and articles but I found them very clumsy. After going through those sites, I noted down the points in a easy way so here I am sharing that unde…
Want to learn how to record your desktop screen without having to use an outside camera. Click on this video and learn how to use the cool google extension called "Screencastify"! Step 1: Open a new google tab Step 2: Go to the left hand upper corn…
We’ve all felt that sense of false security before—locking down external access to a database or component and feeling like we’ve done all we need to do to secure company data. But that feeling is fleeting. Attacks these days can happen in many w…
Suggested Courses

926 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question