Php VS Hack benchmarks

Current benchmark data was generated on Wed Sep 28 2022, full log can be found HERE

CONTRIBUTIONS are WELCOME!

[x86_64][2 cores] Intel(R) Xeon(R) Platinum 8370C CPU @ 2.80GHz (Model 106)

* -m in a file name stands for multi-threading or multi-processing

* -i in a file name stands for direct intrinsics usage. (Usage of simd intrinsics via libraries is not counted)

* -ffi in a file name stands for non-stdlib FFI usage

* (You may find time < time(user) + time(sys) for some non-parallelized programs, the overhead is from GC or JIT compiler, which are allowed to take advantage of multi-cores as that's more close to real-world scenarios.)

binarytrees

Input: 18

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
hacklang 1.hack timeout 0.0ms 0.0MB 0ms 0ms hhvm 4.169.0
php 1.php timeout 0.0ms 0.0MB 0ms 0ms php 8.1.10

Input: 15

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
hacklang 1.hack 1619ms 2.3ms 193.4MB 1547ms 37ms hhvm 4.169.0
php 1.php timeout 0.0ms 0.0MB 0ms 0ms php 8.1.10

helloworld

Input: QwQ

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
php 1.php 40ms 1.0ms 47.4MB 12ms 12ms php 8.1.10
hacklang 1.hack 770ms 5.4ms 171.3MB 714ms 26ms hhvm 4.169.0

merkletrees

Input: 17

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
hacklang 1.hack timeout 0.0ms 0.0MB 0ms 0ms hhvm 4.169.0
php 1.php timeout 0.0ms 0.0MB 0ms 0ms php 8.1.10

Input: 15

lang code time stddev peak-mem mem time(user) time(sys) compiler compiler/runtime
hacklang 1.hack 1787ms 4.2ms 201.0MB 1723ms 37ms hhvm 4.169.0
php 1.php timeout 0.0ms 0.0MB 0ms 0ms php 8.1.10