RE: New Connection for Each Query
Date: Wed, 11 Jun 2008 12:32:16 -0400
Depending on what the application is emitting as a connection string, it may be possible to have the listener on the appropriate port route your connection request to a custom daemon that deals off your connection to an already running connection to an oracle instance.
Basically you would use a fake INSTANCE name to get to that port if you also wanted to support regular connections to a real INSTANCE on running on that database.
One issue would be the schema name connected to. If this is a read only query and always of the same schema that is a modest problem.
Security issues may arise, but you can put string input limits on the daemon to prevent sql injection issues.
This has the potential to relieve the connection overhead.
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Charlotte Hammond
Sent: Monday, June 09, 2008 7:10 AM
Subject: New Connection for Each Query
I have inherited an application which opens a new connection to the database every single time it executes a query. The CPUs are all maxed out despite the fact that each individual query is trivial and runs << 1 second. I'm guessing that it's the load of establishing all these connections all the time which is causing the problem.
1. How can I confirm/refute this guess?
2. Assuming that this is the problem (and that I have no access to change the application source code), what can I do? Can shared server / CMAN help here at all? Anything else?
Any suggestions very much appreciated!
http://www.freelists.org/webpage/oracle-l Received on Wed Jun 11 2008 - 11:32:16 CDT