It's probably not a big help at the moment, but if your friends had mock pieces of the application for testing, they could isolate each part in turn and do benchmarking that way.

For example, when testing something like a libnet module, it's a whole lot easier to whip up a fake Socket module that does exactly what you want than it is to work with all sorts of network configurations. So they could have a fake database object, a fake web server object, and so forth. The performance isn't quite real-world, but if they have enough fake pieces, they can benchmark each real piece in isolation. That can be handy.

Hey, testing can't solve everything, but this is a place it can help.

In reply to Re: performance of LAMP-system by chromatic
in thread performance of LAMP-system by bjelli

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.