Re^4: A way to see how much 'memory' a program will take up in, say, mod

See, I've read both of those - one cover-to-cover (in dead-tree format) - but while they talk a lot about how to optimize mod_perl, there's nothing I've found that says 'type this to see how much memory your program will take up'.

Comment on Re^4: A way to see how much 'memory' a program will take up in, say, mod_perl, so I can start to optimize it?

Replies are listed 'Best First'.
Re^5: A way to see how much 'memory' a program will take up in, say, mod_perl, so I can start to optimize it? by perrin (Chancellor) on Feb 19, 2009 at 20:28 UTC
Well, that should tell you something. :) There is no way to predict it with any accuracy. I think the perlfaq spells this out pretty clearly too. What you have to do is run your program with your real data, see how big it is, and then make changes and repeat. There are some common culprits for large programs, and I believe they are all described in those docs, as well as ways of measuring the size of a running program. There's way to measure the size of a non-running program. It is very data dependent.	[reply]

Replies are listed 'Best First'.

Re^5: A way to see how much 'memory' a program will take up in, say, mod_perl, so I can start to optimize it?
by perrin (Chancellor) on Feb 19, 2009 at 20:28 UTC

Well, that should tell you something. :)

There is no way to predict it with any accuracy. I think the perlfaq spells this out pretty clearly too. What you have to do is run your program with your real data, see how big it is, and then make changes and repeat.

There are some common culprits for large programs, and I believe they are all described in those docs, as well as ways of measuring the size of a running program. There's way to measure the size of a non-running program. It is very data dependent.

[reply]