[Catalyst] Catalyst for (really) big applications

Matt S Trout dbix-class at trout.me.uk
Fri May 19 14:51:43 CEST 2006

Marcello Romani wrote:
> Perrin Harkins ha scritto:
>> Marcello Romani wrote:
>>> The two apache processes take up almost 200mb of ram just before the 
>>> first request. This value grows up to more than 250MB after list()ing 
>>> some tables (with paging).
>> That sounds really high to me.  I'm used to processes about 1/10th that 
>> size in most of my mod_perl apps.
> You didn't quote the fact that my app had about 40/50 modules (not 
> counting external modules like Class::DBI, etc.).
> Also, while I haven't done explicit tests about it, apache configuration 
> might have an impact on process size.
> A hint that this could apply to my case is the fact that running the 
> same app with the catalyst test server took much less memory (30/40 MB 
> if I recall correctly).
> Anyway, as I said I don't have the code anymore and unfortunately I 
> don't recall the numbers involved exactly enough to prove something.
> Unless I do some (fresh) tests, I can't provide any more (euro)cents to 
> this thread. I hope I'll have time to.

30/40Mb sounds much more sensible - and in a *n?x forking environment rather 
than windows+ithreads most of this will hopefully be COWed across multiple 
httpd children / fastcgi handlers so you're only going to take most of that 
hit once per application (and with multiple apps in a single mod_perl at least 
some of it only once per entire httpd)

      Matt S Trout       Offering custom development, consultancy and support
   Technical Director    contracts for Catalyst, DBIx::Class and BAST. Contact
Shadowcat Systems Ltd.  mst (at) shadowcatsystems.co.uk for more information

+ Help us build a better perl ORM: http://dbix-class.shadowcatsystems.co.uk/ +

More information about the Catalyst mailing list