By "same PC" to run a test under Windows vs. Linux, I meant classic dual boot and GRUB as I have, but perhaps virtualization is no longer a hindrance, and, moreover, not in this case. Because I compiled llil2grt.cpp in both OSes (command line and options you advised), here's what I got:

$ ./llil2grt big1.txt big2.txt big3.txt >out.txt
llil2grt start
get_properties      CPU time : 3.67015 secs
emplace set sort    CPU time : 1.19724 secs
write stdout        CPU time : 1.52074 secs
total               CPU time : 6.3882 secs
total        wall clock time : 6 secs

>llil2grt.exe big1.txt big2.txt big3.txt >out.txt
llil2grt start
get_properties      CPU time : 5.577 secs
emplace set sort    CPU time : 1.675 secs
write stdout        CPU time : 2.484 secs
total               CPU time : 9.736 secs
total        wall clock time : 10 secs

[download]

Same relative difference I observe running Perl script. So looks like it's not an issue of Perl and Strawberry version you asked me about (which is latest available "5.32.1.1-64bit-PDL", BTW). I, further, compiled llil2grt.cpp using minGW shell and g++ which came with older 5.26 Strawberry, and got same 10 secs.

I'm clueless why this PC is slow with Windows. Perhaps either MS or Dell issued a patch in recent years to address Kaby Lake CPU (mine is i5-7500T) "vulnerability"? I vaguely remember it was said performance would suffer if such patch to guard against mythical attackers would be applied. Just a guess, sorry if it's ridiculous. On the other hand, J script performs the same in both OSes.

Speaking of which, to return to "interpreted language is faster than compiled C++" -- of course it's dataset bias to a large extent. I ran test with "long" files from another test file generator you suggested previously:

$ ./llil2grt long1.txt long2.txt long3.txt >out.txt
llil2grt start
get_properties      CPU time : 0.559273 secs
emplace set sort    CPU time : 0.004393 secs
write stdout        CPU time : 0.003275 secs
total               CPU time : 0.567 secs
total        wall clock time : 1 secs

$ jconsole llil.ijs long1.txt long2.txt long3.txt out_j.txt
Read and parse input:    1.50791
Classify, sum, sort:     0.70953
Format and write output: 0.00430393
Total time:              2.22175

$ diff out.txt out_j.txt
$

[download]

(NUM_LENGTH changed to 10, otherwise same code)

In reply to Re^3: Rosetta Code: Long List is Long (faster) by Anonymous Monk
in thread Rosetta Code: Long List is Long by eyepopslikeamosquito

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.