"Jim Kennedy" <kennedy-downwithspammersfamily_at_attbi.net> wrote in message news:<_ATSc.242595$a24.58689_at_attbi_s03>...
> "DK" <dakight_at_bellsouth.net> wrote in message
> news:K6TSc.25$ii.5_at_bignews5.bellsouth.net...
> > I have a developer who would like for the open_cursors to be set to 2000.
> > He tells me that he will open his cursor once for the life of his
> > application to avoid reparsing his sql statements by oracle. He's using
> > bind variable in his code. Is there an advantage of leaving these cursors
> > open for the duration of the application versus just having Oracle search
> > the shared pool for the matching sql?
> >
> This practice helps scalability of the application. You require less CPU
> cycles and will have better performance. This is a common practice. Your
> machine will use more RAM as each process will possibly need more ram to
> run, but you will have less memory thrashing if you have sufficient ram on
> the server.
However, everything has some limit. I have here an application that
serves for 4000 users, at the end of the day there is 400.000 open
cursors. Sometime is a good idea to close cursor.
--
Dusan Bolek
http://www.db-support.com
Email: spambin_at_seznam.cz
Pls add "Not Guilty" to the subject, otherwise your email will face an
unpleasant end as SPAM.
Received on Fri Aug 13 2004 - 01:19:11 CDT
