Hello guys,
after fiddling around with Catalyst+DBIx starup time, here comes my next
issue:
Is there some way to tune Catalyst to use less RAM? Is there even some
kind of explanation for the really FAT memory footprint?
Currently, our project allocates 330MB RAM right after startup (with
myproject_server.pl or fastcgi). Over the time this is getting worse;
some month after the projects start it used about 80MB and we think with
some additional controllers and stuff it will need over 500MB. I know
there is some advent calendar entry about restartig the catalyst-process
when it reaches a memory limit (what is good - our processes tend to
grow up to 1GB), but this doesn't help at startup.
Is this normal behaviour?
The problem is, we use multiple instances of the application. So every
customer has his own catalyst instance with own database and - of course
- own fastcgi-process. Currently we are running it on a machine with
16GB of RAM and will soon get to the physical and budgetary limits.
Is Catalyst just not intended for this kind of use (and more like "one
server, one site") or is there some black magic we just haven't found yet?
Btw: Neither reducing the count of the DBIx-models nor disabling the
debug-mode does have an impact on memory footprint.
Thanks and regards,
Thomas Weber
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
