If I could upvote this another ten times it wouldn't be enough.

It took me a long time to learn this (and I didn't until long after I quit writing assembler for a living). "As fast as possible" is meaningless unless you're in a situation where you can calculate a theoretical maximum speed easily - and I've never had a project where that was possible.

You may need to make it clear when you ask for the minimum acceptable performance that you're not shooting to perform at that speed, but that you need to know the minimum to decide on a basic approach: you may be able to say unequivocally that the speed isn't obtainable with your current hardware/network/software stack, or that you know that you'll need a distributed architecture to meet the desired performance goals. Without a hard metric, you might make the assumption that a 10-second response time is acceptable, because that's "as fast as possible" on a single laptop machine, when at least sub-second response is required.

You're asking to avoid a waste of money and time developing an insufficient solution. You may well be able to do a lot better, but you need to know what's necessary.

In reply to Re^5: As Efficient as Possible by pemungkah
in thread As Efficient as Possible by mr_p

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.