Although this does not directly address your issue it just might give
you some new ideas for scaling up Catalyst. I agree with many here
that you should profile your app for leaky culprits. Since you don't
give much detail on you platform or other details it's little what one
can recommend.
Anyway
Neo [GC] wrote:
> Currently, our project allocates 330MB RAM right after startup (with
> myproject_server.pl or fastcgi).
What OS?
Where do you get the 330MB figure from?
> Over the time this is getting worse;
> some month after the projects start it used about 80MB and we think
> with some addi
Ignoring the rest of your mail which J has given a nice reply to..
Neo [GC] wrote:
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
wit
On Tue, Feb 17, 2009 at 6:44 AM, Neo [GC] wrote:
> 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,
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
m
