pileofrogs,
Typically you profile an application to identify bottlenecks. Then, you write one or more alternatives to the sore spots. Next, you synthesize the input data required by that those routines which is something normally the full application would do. Finally, you Benchmark them.

It sounds like you have two issues. The first is that you don't want to wait until you have a complete application before benchmarking as you suspect you already know where your bottlenecks will be. The second is you can't think of a good way to synthesize the input without having a full blown application.

I am not sure the approach you are going in is the right one. If I have understood correctly, your ultimate dilema is making an up front design decision about your architecture. It is hard to see why the normal process won't work for you. Perhaps you need to give a more concrete explanation. Regarding your idea about tying your benchmarking to your test suite, it sounds like you want Mock::App (non-existent) where the majority of your API is just stubs but the routines that you are interested in testing and benchmarking are complete. I really don't see what this buys you since a good benchmark should really be comparing the smallest possible variations of functionally equivalent routines.

Update: I see your response and will reply with links and further advice when time permits. For starters, you can take a look at the planning and design phases of the software development life cycle (SDLC).

Cheers - L~R

In reply to Re: Benchmarking Strategy? by Limbic~Region
in thread Benchmarking Strategy? by pileofrogs

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.