Perfomance is a word often used with a very narrow meaning.
Other measures of performance people should be more concerned about:
- Programmer's cost vs. output (quality, quantity, speed) vs. happiness (sustainability, burnout) performance (relevant to why we use Perl and not assembly)
- Latency and response (perceived performance very critical in the webapp/GUI world)
- load (running the program once is OK, but 100 times on the same machine? relates to both latency and throughput)
- disk usage (important in some specialized fields, for example high end databases)
- throughput (the "regular" performance, really only worth it when it comes to batch processing *HUGE* amounts of data. why you might want to use assembly and not Perl)
- maintainability, readability, debuggability - think of this as robustness performance - how your app performs in the course of it's entire life, with respect to changing priorities/requirements/staff.
- ...
Performance is not overrated - it's what determines the cost/value ratio of any piece of work. What is overlooked is how you balance the various aspects of performance to maximize effectiveness (cost/value ratio).
Also, wrt throughput, remember that typically when someone runs a long program they tend to run it 10 times before on smaller data, just to make sure it works like they expected. I tend to try to make sure that I can slice that chunk of time by giving nice progress reports, and decent defaults/warnings/hooks, thus usually halving the truly total time, instead of making sure i can fudge data a into data b in the minimum number of opcodes.
Anyway, my point is: Balance is everything.
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.