Duh, I shouldn't post in a hurry. I just glanced through
that.
Have you looked at RE: RE: RE: big performance gain giving some CGI.pm performance
tips from merlyn?
But in any case all that that post gave were performance
numbers. There is also cost to consider. Having people
write new code costs money. Having people audit that code
costs money. Having someone find the hole you missed and
delete your customer database costs a lot of money.
In the mean-time more boxes are cheap, in 18 months the
processor will be twice as fast anyways, and you cannot
predict where the performance bottlenecks will be. It is
more important to have a sane architecture within which
you can identify design mistakes and fix them than it is
to squeeze performance out right away. Using off the
shelf modules makes it easier to do that.
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.