I agree - a good response to the original question is to recommend the biggest, fastest computer(s) available on the market today. Realistically, though, this is not feasable, so the question becomes a business one, as in "What hardware do we think the customer will buy?" From a development role, the important thing is to make sure that the software runs acceptable on the system that is recommended (with mod_perl that probably means a lot of RAM). Also it is useful to recommend a configuration that will be easy to support.

Given all of this, it is probably best to take this question from a business/sales standpoint and ask the question "what is the best way to make money off this recommendation?" Spending a lot of time benchmarking can eat into profits without providing a tangible value for the customer, so in general it may be best to test as few configurations as possible.

Also, a good solution might include suggesting lots of horizontal scalability - instead of a single server, why not recommend a horizonatally scalable solution using a load balancer and a couple of less powerful computers rather than one large server? This way, if additional hardware is required to meet performance expectations, additional (less expensive) servers can be added to the configuration. This configuration may also be easier to maintain, as individual servers can be swapped out, upgraded, etc without causing a system outage.

techy
When art critics get together they talk about Form and Structure and Meaning. When artists get together they talk about where you can buy cheap turpentine. -- Pablo Picasso

In reply to Re^2: How to recommend hardware to customers? by techy
in thread How to recommend hardware to customers? by amonroy

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.