Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

ARM Parrot benchmarks II 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Your C code searched a different (larger) space than the Perl and Parrot versions.

    And you used only a single space in each.

    Suggestion: run the test for spaces 1e4, 2e4, and 3e4 for all three languages. Then we can do some comparisons.

    For additional bonus bring in Python and Ruby, maybe even Java.

    For additional additional bonus, do not compare only running times but also memory use and "executable" (whatever that means for each language) sizes.

    • well - as I stated beforehand, the tests are preliminary to get a first impression anyway. For what we will try (oo framework for gui programming) I will have to set up a more elaborate test case anyway. What I am looking for is the performance when the instruction and data caches start to overflow (at 32kb each, this should happen rather soon). Then I will have real performance data :) btw, the numbers in the "ps" shows the sizes: 4.7M for parrot, 1.6M for perl.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.