| 4/21/2006 1:51:41 PM |
Hi Paul,
I have searched through the forums and found many threads were you mention connection pooling being handled automatically by the ADO.NET provider. My question is specifically in working with a web application using an Oracle database.
In some preliminary load testing of our web application we are noticing that Oracle only have one session for the aspnet_wp.exe worker process, and this is worrying us as to the performance of the app should a bunch of simultaneous reads or writes start happening and we have users lagging out waiting for the connection to free up....
Could you shed a little light as to the opportunities to implement some formal connection pooling architecture?
Thanks, Brandon |
| 4/21/2006 2:07:04 PM |
Hi Brandon:
The ORMapper uses normal ADO.NET and best practices -- which should (and does in my experience) automatically enable connection pooling, assuming the specific ADO.NET provider supports it (as all major ones do). For the builtin .NET Oracle ADO.NET provider, connection pooling is supported, and is the default, so it should be automatic -- see this MSDN article for more. For the ORMapper and best practices to enable this, that means opening connections as late as possible and closing them as quickly as possible -- this is one best practice that is hard to argue with, and it is what the ORMapper does.
Now here's another spin on what you are seeing. If connection pooling is being used, and if you aren't truly getting simultaneous database hits, then it would make perfect sense that there would only be one actual Oracle connection. On the other hand, if connection pooling is not being used, then its highly unlikely that you would ever see just one actual Oracle connection. So if anything, what you are seeing tends to support that connection pooling is being used, but your load tests may not be enough.
Thanks, Paul Wilson
|