JayBonci hit the nail on the head. I have used this approach a few times and the benefits were substantial. But, that's because I only used this approach in cases where the data was generally quite static.
You *could* regenerate the html whenever it is modified. If that fits your application, then go for it. But if you're going to update a dozen times every minute, it's probably not going to help.
Also remember that when you keep everything dynamic, it's that much easier to redesign all your output and make global changes to your data. With your flat file approach, you'd need to change your code or templates and then somehow 'republish' all your static files. That can be a pain.
If you're looking to speed up your dynamic Perl-driven stuff, take a closer look at mod_perl. Also, tweak your MySQL piece for optimization. Make sure you have appropriate keys in place to make for faster lookups on tables, etc.
Good luck!
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.