Re: Downside to ora_envhp=>0 to fix OCIHandleAlloc(OCI_HTYPE_ERROR) problem

On 01/26/2011 02:27 PM, John Scoles wrote:
> On 25/01/2011 8:21 PM, William Ward gmail wrote:
>> In regards to this thread:
>> http://www.mail-archive.com/[email protected]/msg32115.html
>> (found via google)
>>
>> I'm having the same problem at $JOB and before we throw ora_envhp=>0
>> into our connect attribute, we were wondering if this will cause
>> performance issues?  Is there a downside to ora_envhp that isn't
>> described in the thread?
> Yes that will case some performance slow downs as it will have to 
> connect and recreate the environment(connection) for each dbi->connect().
> Normally it will reuse the environment(connection) and just create a 
> new session for each dbi->connect().

FWIW I'm getting excellent dbi->connect()  performance with mod_perl, 
Apache DBI and ora_envhp=>0. The database connections stay intact 
(unless of course there is a shutdown/startup).

After the database is bounced, dbi->connect() connections take approx 25 
milliseconds (no OCI_HTYPE_ERROR, and no apache restart required) . But, 
after the connections are cached, each subsequent dbi->connect() 
typically takes less than 1 millisecond.

I suppose there is some overhead with the OCI environment recreation but 
nothing noticeable for our application.

Tim