1 : At a glance - Are the Erlang HiPE programs faster?

Each chart bar shows, for one unidentified benchmark, how much the fastest Erlang HiPE program used compared to the fastest C gcc program.

(Memory use is only compared for tasks that require memory to be allocated.)


These are not the only compilers and interpreters. These are not the only programs that could be written. These are not the only tasks that could be solved. These are just 10 tiny examples.

 2 : Approximately - Are the Erlang HiPE programs faster?

Each table row shows, for one named benchmark, how much the fastest Erlang HiPE program used compared to the fastest C gcc program.

(Memory use is only compared for tasks that require memory to be allocated.)

 Erlang HiPE used what fraction? used how many times more? 
Benchmark Time Memory Code
 regex-dna±1/2
 binary-trees1/2
 pidigits ±
 spectral-norm ±
 k-nucleotide10×1/2
 fannkuch-redux10× ±
 reverse-complement18×
 n-body22× ±
 fasta †28× 1/2
 mandelbrot29× ±
 Erlang HiPE used what fraction? used how many times more? 
Time-used  |-  |---  25% median  75%  ---|  -|
(Elapsed secs)10×22×29×29×

† possible mismatch - one-core program compared to multi-core program.

± read the measurements and then read the program source code.

 3 : Measurements - Are the Erlang HiPE programs faster?

These are not the only tasks that could be solved. These are just 10 tiny examples. These are not the only compilers and interpreters. These are not the only programs that could be written.

For each named benchmark, measurements of the fastest Erlang HiPE program are shown for comparison against measurements of the fastest C gcc program.

Program Source Code CPU secs Elapsed secs Memory KB Code B ≈ CPU Load
 regex-dna 
Erlang HiPE39.8211.17283,5521058  93% 90% 89% 86%
C gcc6.342.67290,7922579  96% 76% 84% 67%
 binary-trees 
Erlang HiPE46.2612.88617,852499  99% 88% 88% 86%
C gcc9.682.97105,024906  93% 77% 87% 72%
 pidigits 
Erlang HiPE14.9414.9425,040559  1% 1% 1% 100%
C gcc2.492.502,140448  100% 0% 1% 0%
 spectral-norm 
Erlang HiPE71.4518.1920,904747  98% 98% 98% 99%
C gcc7.861.981,704569  99% 100% 99% 99%
 k-nucleotide 
Erlang HiPE351.76124.55980,820932  69% 81% 58% 77%
C gcc36.5812.35131,9041535  37% 71% 95% 94%
 fannkuch-redux 
Erlang HiPE405.52102.5312,9441038  100% 98% 98% 100%
C gcc39.4910.061,388910  99% 99% 95% 100%
 reverse-complement 
Erlang HiPE21.0811.00844,9201302  43% 50% 51% 50%
C gcc0.860.60251,368741  95% 84% 44% 15%
 n-body 
Erlang HiPE225.14225.2112,9481399  100% 1% 1% 1%
C gcc10.3810.397361490  0% 100% 1% 1%
 fasta 
Erlang HiPE49.8749.8824,1161164  1% 1% 1% 99% †
C gcc5.291.812,3521914  89% 53% 54% 100% †
 mandelbrot 
Erlang HiPE628.04162.01635,812613  98% 97% 97% 97%
C gcc22.405.6128,988799  100% 100% 100% 100%
 fasta-redux 
No program
C gcc0.020.02?1402  0% 0% 0% 100%

† possible mismatch - one-core program compared to multi-core program.

 4 : Are there other Erlang HiPE programs for these benchmarks?

Remember - those are just the fastest Erlang HiPE and C gcc programs measured on this OS/machine. Check if there are other implementations of these benchmark programs for Erlang HiPE.

Maybe one of those other Erlang HiPE programs is fastest on a different OS/machine.

 5 : Are there other faster programs for these benchmarks?

Remember - those are just the fastest Erlang HiPE and C gcc programs measured on this OS/machine. Check if there are faster implementations of these benchmark programs for other programming languages.

Maybe one of those other programs is fastest on a different OS/machine.

 Erlang HiPE : concurrent real-time distributed fault-tolerant software 

"Four-fold Increase in Productivity and Quality: Industrial-Strength Functional Programming in Telecom-Class Products" pdf

All you wanted to know about the HiPE compile (but might have been afraid to ask)

The development of the HiPE system: design and experience report

Erlang/OTP 17 [erts-6.2] [source] [async-threads:10] [hipe] [kernel-poll:false]

Home Page: http://www.erlang.org/

Download: http://www.erlang.org/download.html

Revised BSD license

  Home   Conclusions   License   Play