To paraphrase Sherlock Holmes,
It is a cardinal sin to optimize before one has data.
Trimming back URLs would indeed same 8 bytes here and there, but does onyone (besides possibly
vroom or someone on the Everything Engine team) have measurements that suggest that network traffice is anywhere near a bottleneck? If so, an optimization focused on byte-level traffic might be warranted (though a scheme based on compressing redundant whitespace out of HTML would have a much bigger payoff).
I rather suspect, based on a bit of experience with a similar engine, that the server is CPU bound.
A well-intentioned thought, but one that needs to be pursued after measurement.
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.