Python Interpreters Benchmarks
x64 ArchLinux : AMD® Ryzen 7 4700U®

 meteor-contest benchmark N=2,098

Each chart bar shows how many times slower, one ↓ meteor-contest program was, compared to the fastest program.

These are not the only programs that could be written. These are not the only compilers and interpreters. These are not the only programming languages.

Column × shows how many times more each program used compared to the benchmark program that used least.

    sort sortsort
  ×   Program Source Code CPU secs Elapsed secs Memory KB Code B ≈ CPU Load
1.0PyPy 3 #2 0.640.6574,0281443  3% 2% 100% 2% 0% 6% 2% 3%
1.0PyPy 3 0.670.6773,5881540  0% 0% 1% 100% 3% 2% 0% 0%
1.0PyPy 2 #2 0.670.6780,9721485  4% 0% 1% 99% 0% 4% 0% 0%
1.0PyPy 2 0.670.6881,2481579  100% 1% 0% 0% 0% 3% 0% 0%
1.9Pyston #2 1.231.238,8681485  2% 2% 1% 0% 2% 1% 0% 100%
2.1Nuitka #2 1.351.3511,3921443  1% 0% 0% 0% 1% 100% 0% 0%
2.3Pyston 1.491.498,3641579  4% 2% 0% 100% 1% 1% 0% 1%
2.4PyPy 2 #3 1.521.5279,1721354  100% 0% 1% 0% 1% 0% 3% 1%
2.4PyPy 3 #3 1.551.5571,9161334  100% 0% 0% 1% 1% 1% 0% 2%
2.4Python development version #2 1.551.559,5121443  0% 0% 0% 100% 1% 1% 1% 0%
2.6Python 3 #2 1.701.7010,9641443  1% 1% 1% 0% 0% 0% 0% 99%
2.7Nuitka 1.731.7411,2641540  100% 1% 0% 0% 1% 0% 0% 1%
2.8Graal 5.671.83873,8081540  11% 74% 44% 18% 51% 13% 20% 86%
2.9Graal #2 5.771.84899,7241443  57% 18% 11% 77% 14% 70% 3% 67%
3.2Python development version 2.052.059,3601540  0% 100% 1% 0% 1% 1% 0% 0%
3.3Python 2 #2 2.142.146,8281485  0% 0% 100% 0% 0% 0% 0% 1%
3.4Pyston #3 2.202.2110,5761354  1% 1% 100% 0% 1% 0% 0% 0%
3.5Python 3 2.232.2310,8961540  0% 0% 1% 100% 0% 0% 1% 1%
3.6Cython #3 2.352.3511,1841334  100% 0% 0% 0% 2% 1% 0% 0%
4.0Nuitka #3 2.552.5513,1841334  0% 100% 1% 0% 1% 0% 0% 0%
4.1Python development version #3 2.622.6211,2321334  0% 0% 0% 1% 1% 2% 100% 0%
4.3Python 3 #3 2.762.7712,8841334  100% 0% 0% 0% 1% 0% 0% 0%
4.6Python 2 2.942.946,4361579  0% 100% 1% 0% 0% 0% 0% 1%
5.7Python 2 #3 3.693.697,3441354  0% 100% 0% 0% 1% 1% 1% 0%
7.5Graal #3 15.044.841,102,2641334  63% 9% 64% 30% 71% 6% 22% 52%
8.5Jython #2 9.645.513,4321485  58% 22% 17% 13% 14% 12% 24% 17%
11Jython #3 12.136.843,5881354  13% 21% 26% 8% 13% 72% 17% 10%
11Jython 12.377.053,6641579  16% 17% 24% 21% 70% 17% 8% 7%
44RustPython #2 28.2728.2716,4001443  35% 1% 1% 0% 66% 0% 0% 1%
56RustPython 36.0836.0816,0441540  1% 1% 1% 1% 0% 1% 0% 100%
missing benchmark programs
IronPython No program
Shedskin No program
Numba No program
MicroPython No program
Grumpy No program

 meteor-contest benchmark : Search for solutions to shape packing puzzle

This is a contest - different algorithms may be used.

You are expected to diff the output from your program N = 2098 against this output file before you contribute your program.

The Meteor Puzzle board is made up of 10 rows of 5 hexagonal Cells. There are 10 puzzle pieces to be placed on the board, we'll number them 0 to 9. Each puzzle piece is made up of 5 hexagonal Cells. As different algorithms may be used to generate the puzzle solutions, we require that the solutions be printed in a standard order and format. Here's one approach - working along each row left to right, and down the board from top to bottom, take the number of the piece placed in each cell on the board, and create a string from all 50 numbers, for example the smallest puzzle solution would be represented by

00001222012661126155865558633348893448934747977799

Print the smallest and largest Meteor Puzzle 50 character solution string in this format to mimic the hexagonal puzzle board:

0 0 0 0 1 
 2 2 2 0 1 
2 6 6 1 1 
 2 6 1 5 5 
8 6 5 5 5 
 8 6 3 3 3 
4 8 8 9 3 
 4 4 8 9 3 
4 7 4 7 9 
 7 7 7 9 9 

The command line parameter N should limit how many solutions will be found before the program halts, so that you can work with just a few solutions to debug and optimize your program.

Diff program output N = 2098 against the output file to check the format is correct.

The Meteor Puzzle and 3 Java puzzle solvers are described in "Optimize your Java application's performance" (pdf).

Revised BSD license

  Home   Conclusions   License   Play