> Has anyone performed even rudimentary benchmarking of the various implementations of P6?

To give a sense of #perl6 awareness and use of benchmarking, you could browse this search for "benchmark" mentions on #perl6. Nearly 300 days in the last 7 years include at least a mention. From the most recent page of results, 7 of the 13 matches involving 8 folk relate to benchmarking improvements or benchmark results rather than mere discussion. Imo the mandelbrot script is particularly interesting.

From another angle, here's a slideshow about the performance of Rakudo (a P6 compiler).

> I'm still attracted to (what I remember of) the P6 syntax, but for the type of applications I mostly write -- generally cpu-bound -- cool syntax isn't sufficient justification for taking a 10x or even 5x performance hit over P5.

Right. Speedwise, in some ways current P6 implementations are in a position analogous to Python or Ruby, especially earlier versions. It's entirely possible that no current P6 implementation is yet in the same planetary system, let alone ballpark, for what it sounds like you need.

That said, in theory, @Larry have tackled the issue of speed in P6, including at the cpu level, from the start. For example, in theory, P6 autothreading is supposed to automatically distribute a lot of computation over the multiple CPUs in multicore hardware. However, following good dev practice, a lot of P6 optimization has been left till "the last mile" -- ie hasn't happened yet.

as a minimalistic start I'd suggest...

Perl6 needs contributors much more than it needs ideas. That's why I posted this comment. It would be awesome if you visited #perl6 on freenode with an open mind and volunteered to try to set up one of the benchmarks you mention for one compiler and then post about your experience here. Maybe using japhb++'s perl6-bench project, a P6 workbench for doing comparative benchmarking?

In reply to P6 benchmarks (was Re^10: Hockey Sticks) by raiph
in thread Hockey Sticks by raiph

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.