Oleg Bartunov writes:
> On Thu, 14 Oct 1999, Perrin Harkins wrote:
>
> > Date: Thu, 14 Oct 1999 17:53:15 -0700 (PDT)
> > From: Perrin Harkins <[EMAIL PROTECTED]>
> > To: Jeffrey Baker <[EMAIL PROTECTED]>
> > Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
> > Subject: Re: More on web application performance with DBI
> >
> > On Thu, 14 Oct 1999, Jeffrey Baker wrote:
> > > Zero optimization: 41.67 requests/second
> > > Stage 1 (persistent connections): 140.17 requests/second
> > > Stage 2 (bound parameters): 139.20 requests/second
> > > Stage 3 (persistent statement handles): 251.13 requests/second
> >
> > I know you said you don't like it because it has extra overhead, but would
> > you mind trying stage 3 with prepare_cached rather than your custom
> > solution with globals? For some applications with lots of SQL statements,
> > the prepare_cached appraoch is just much more manageable.
>
> Some databases doesn't support caches of prepared plans.
> PostgreSQL for example.
Or Sybase.
Though with Sybase you could open multiple connections to achieve the
same result (at the risk of getting deadlocks depending on what you
are trying to do!)
Michael
--
Michael Peppler -||- Data Migrations Inc.
[EMAIL PROTECTED] -||- http://www.mbay.net/~mpeppler
Int. Sybase User Group -||- http://www.isug.com
Sybase on Linux mailing list: [EMAIL PROTECTED]
