I am at a similar point in the planning of a project too; having finished over a month of interviews and page specifications, am about to roll up the sleeves.

I'm planning on using HTML::Template, CGI::Application, and DBI with MySQL and using MySQL's query cache. Cron will generate images and possibly pdfs or word documents at night or when modified, the main load being searches on a product catalog by up to 2000 distributors, and the templating.

I am leaning toward mod_perl for performance, though because of very limited time to build it, may develop without mod_perl (but with strict) first.

I'm wondering about how much speed is gained in maintaining a persistent connection with Apache::DBI, and with templates being cached, so I can make an better decision about using mod_perl. I know it's great, and have used it, but I don't have time to wrestle with CGI::Application and restart the server a hundred times. I'm looking at. Application Performance using DBI and mod_perl now.

I also was just looking at The HTML::Template page and it mentions a 90% speed increase using Template caching in mod_perl, plus a way to save a ton of memory by sharing the template cache between the processes.

In reply to Re: Database driven web content: live or tape? by mattr
in thread Database driven web content: live or tape? by talexb

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.