talexb has asked for the wisdom of the Perl Monks concerning the following question:
I'm working with a large Perl application that has a couple of different run modes. One of these modes is a full-bore mode and it needs to call in lots of modules. Another mode is much simpler (think of it as read-only) and doesn't require nearly as many modules.
I've looked in the Perl man pages, looked in the Camel, googled a little and used Super Search here on PM but haven't yet come across anything that will help me reduce the memory footprint (by not pulling in modules that aren't used).
The only solution that I can think of is to only use the modules if we're running in the 'full-bore' mode. Does that make sense? Any other suggestions, comments?
Alex / talexb / Toronto
"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Reducing Perl's memory footprint depending on run mode
by BrowserUk (Patriarch) on Apr 21, 2005 at 15:27 UTC | |
|
Re: Reducing Perl's memory footprint depending on run mode
by cees (Curate) on Apr 21, 2005 at 15:56 UTC | |
|
Re: Reducing Perl's memory footprint depending on run mode
by dragonchild (Archbishop) on Apr 21, 2005 at 15:06 UTC | |
|
Re: Reducing Perl's memory footprint depending on run mode
by ides (Deacon) on Apr 21, 2005 at 14:55 UTC | |
by dave_the_m (Monsignor) on Apr 21, 2005 at 15:12 UTC | |
by perrin (Chancellor) on Apr 21, 2005 at 15:13 UTC | |
by ides (Deacon) on Apr 25, 2005 at 14:53 UTC | |
by DrWhy (Chaplain) on Apr 21, 2005 at 15:16 UTC |