Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery
 
PerlMonks  

Re^4: Reasons for Using "Perl6" (don't need to earn a living?)

by Tux (Abbot)
on Jan 02, 2018 at 11:27 UTC ( #1206534=note: print w/replies, xml ) Need Help??


in reply to Re^3: Reasons for Using "Perl6" (don't need to earn a living?)
in thread Reasons for Using Perl 6

My speed tests compare different aspects of the languages, but focus on how close pure perl6 can get to perl5 + XS. As perl6 has no XS, that is not really a fair compare, but it aims on getting a general idea of how the perl 6 language itself optimizes performance over time.

Comparing pure perl5 (0.676) to pure perl6 (2.596) shows a factor of 3.8 *today* (2018-01-02). A comparison to perl 5 + XS shows a factor of 130, which is *much* closer than the 350 from August, and that is speed improvement in the language itself. If a process is to be written purely for speed, that might be a consideration to stick to perl 5. If your process however only parses a few thousand lines en development of the program itself is more important that an extra second in parsing the CSV (most processes parse CSV as part of a bigger picture), than reconsidering a look at perl 6 might surprise you. It is quite stable by now.

I also compare the same test to other languages on a daily basis.

One speed improvement in perl 6 that has been really noticable is in the area of parallelization. Something that my tests do not show, as one cannot parse CSV data from a single stream in parallel.


Enjoy, Have FUN! H.Merijn
  • Comment on Re^4: Reasons for Using "Perl6" (don't need to earn a living?)

Replies are listed 'Best First'.
Re^5: Reasons for Using "Perl6" (don't need to earn a living?)
by chromatic (Archbishop) on Jan 03, 2018 at 23:36 UTC
    A comparison to perl 5 + XS shows a factor of 130, which is *much* closer that the 350 from August, and that is speed improvement in the language itself.

    In theory, Rakudo is a language with a better type system than C. In theory, Rakudo has a JIT and shouldn't require you to write XS or C or internals code to optimize things. In theory, a better optimized system wouldn't have to cross the language/ABI/calling conventions boundary of Perl/XS.

    In theory, Rakudo was designed to be easier to optimize (and to require fewer pessimizations) than Perl.

    Now I know as well as anyone that optimizations are difficult and time consuming and need a lot of careful thought and tuning, but parsing and file I/O aren't exotic operations that tax your ability to think of complicated optimization strategies. Rakudo/Moar still being over two orders of magnitude slower than optimized Perl for CSV parsing is not, to me, a ringing endorsement.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1206534]
help
Chatterbox?
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (6)
As of 2018-07-17 22:59 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    It has been suggested to rename Perl 6 in order to boost its marketing potential. Which name would you prefer?















    Results (379 votes). Check out past polls.

    Notices?