[Catalyst] Profiling shows Catalyst::Engine::write slowest ?

Matt S Trout dbix-class at trout.me.uk
Fri Aug 8 02:52:48 BST 2008


On Wed, Aug 06, 2008 at 09:03:35PM -0400, Stef Telford wrote:
> > The question arises, how on earth do I fix/improve these ? From
> > what I assume (dangerous I know), the catalyst engine write is the
> > output from the templating write, how can I improve that speed ? I
> > am using fastcgi on the 'main server' but it's still "as slow".
> > Also the DBD::Pg login could be 'pooled', although I use
> > dbix::class(::schema), has anyone done this ?
> >
> > I am kinda scratching my head on this, any
> > pointers/help/ideas/smacking with manual is appreciated :D Regards
> > Stef
> Hey Everyone,
>     Okay, so, colour me stupid, Compess::Gzip helps with the write
> output delivery (because that's mostly down to the network connection
> speed), however, Catalyst and DBIx::Class Pooling/Persistance ? Anyone
> set this up before ?

If you're using Catalyst::Model::DBIC::Schema then the schema instance
is retained so the connection should be persistent - assuming your db
server doesn't kick you off you'll only connect on the first request
per process that hits the db.

-- 
      Matt S Trout       Need help with your Catalyst or DBIx::Class project?
   Technical Director                    http://www.shadowcat.co.uk/catalyst/
 Shadowcat Systems Ltd.  Want a managed development or deployment platform?
http://chainsawblues.vox.com/            http://www.shadowcat.co.uk/servers/



More information about the Catalyst mailing list