What you should always do is test something which is as similar as possible to what you care about.

That's all it comes down to really.

In this particular case, the big-iron machine *is* slower than your desktop for a single-threaded load (as others have pointed out).

If what you care about is a non-parellisable problem, your home machine *will* run it faster than the big box.

If what you care about is producing numbers which show your big box is fast (which is fair enough, it's fun to play with these things), then do what the others mentioned and run multiple cpu crunchers and aggregate the results.

But this is only CPU, of course. If your problem has a 2Gbyte dataset, the desktop has 1Gb RAM and the big box has plenty, then you'll see a big difference depending on how much RAM you use in your performance test.

So...perf comparisons between hardware come down to how accurately you can model the load you care about. Which is generally limited to how well you understand it and how well you can reproduce 'real world' conditions. (A thousand users on slow modems nibbling away at your app, plus 10% on screaming broadband can produce a very different load to 100 looping procs on another box on your LAN).

In reply to Re: System Performance by jbert
in thread System Performance by Massyn

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.