I already have some reasonably good data about the size of the complied perl code (not the native executable) and how much of it is ours and how much comes from CPAN, etc.; using Devel::Size & Devel::Size::Report. With this analysis it is clear that most of this is our own code. And I really am talking about the size of the compiled code, not data.
Actually, changing the build options did make a big difference. I think excluding threading was the big win. Altogether those options, coupled with a switch to 5.10 from 5.8, saved about 30%.
But even as it stands, the in-memory image include a lot of overhead just for the filenames and module names: about one instance of each of those strings for each executable line of code in the source files.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.