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.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
