use mod_perl;

Probably the biggest hit you're getting is the overhead of the CPAN modules. The Template and DB abstraction layer / rdbms systems are all huge. File::Find is similarly big . You'll get a giant speedup from caching those into memory under some sort of persistent environment.

When you get to production, Apache is also pretty slow/bad. There are far more efficient options now.

My best advice would be to install nginx on port 80 to handle static content, and proxy all dynamic content to your mod_perl app on an alternate port.

Run mod_perl2 + Apache2 on port 8000. Use the registry module on mp2, not the mod_perl handler module -- you should have a fairly transparent migration.

Don't expect to get 16x more performace off mod_perl -- mp will speed you up, but you're still going to suffer from performance bottlenecks at the db level.

Stroring data in xml is a bad decision. You should store it in the DB in some sort of normalized format, then export it to xml or whatever you want as you need it. you're probably doing a lot more parsing and using a lot more diskspace than you should.

In reply to Re: Why can code be so slow? by 2xlp
in thread Why can code be so slow? by freakingwildchild

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.