I have a module with many many packages in it. Its becoming problematic to work in git with conflicts and such. When I split it up into a file per class I get 85 new files. After doing some testing I am seeing that the code calling the split version of my code is now slower than when it called the old the monolithic package. My question is why could this be? Even splitting the code into 10 files shows no performance improvements. Is this best left as is for performance? Is there maybe a middle ground? Any input here is appreciated. Here is what my code looks like: 
package Foo;

package A
our @ISA = qw{Foo};

package B
our @ISA = qw{Foo};

package C
our @ISA = qw{Foo};

package Bar;

package D
our @ISA = qw{Bar}

package E
our @ISA = qw{Bar}

package F
our @ISA = qw{Bar}

...

[download]

In reply to Splitting large module by jimmygoogle

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.