Re: Cached Queries Problem

[prev] [thread] [next] [Date index for 2005/04/28]

From: Michael Peters
Subject: Re: Cached Queries Problem
Date: 14:09 on 28 Apr 2005
David Christensen wrote:
> On Apr 27, 2005, at 11:35 PM, Perrin Harkins wrote:
> 
>> Also, make sure you are not opening any connections or preparing any
>> queries before apache forks.  (Or make sure you close them if you must.)
> 
> 
> One thing that I am doing is trying to preload my Class::DBI subclass in
> apache (just via a use statement). I'm using one of the table-setup
> utility functions rather than hard-coding the fields in, so that may be
> the cause of the problem -- we obviously have to query the database
> before we can pull info out of the system tables.
> 
> I'll try avoiding the preload and let you all know how things work out.

If you don't do the preload then you're modules have to query the
database everytime they are loaded (or at least the first time they are
loaded per apache child) and you don't get the COW benefit.

Don't ditch the preload, just follow perrin's suggestion about closing
the handle at the end of the preload.

        -- 
        Michael Peters
Developer
Plus Three, LP

(message missing)

Cached Queries Problem
David Christensen 01:58 on 27 Apr 2005

Re: Cached Queries Problem
David Christensen 23:34 on 27 Apr 2005

Re: Cached Queries Problem
Perrin Harkins 04:35 on 28 Apr 2005

Re: Cached Queries Problem
David Christensen 14:08 on 28 Apr 2005

Re: Cached Queries Problem
Michael Peters 14:09 on 28 Apr 2005

Re: Cached Queries Problem
David Christensen 14:25 on 28 Apr 2005

Re: Cached Queries Problem
Perrin Harkins 14:30 on 28 Apr 2005

Re: Cached Queries Problem
David Christensen 14:39 on 28 Apr 2005

Re: Cached Queries Problem
Perrin Harkins 14:59 on 28 Apr 2005

Re: Cached Queries Problem
David Christensen 15:20 on 28 Apr 2005

Generated at 10:24 on 04 May 2005 by mariachi v0.52