chameneos-redux benchmark N=6,000,000
Each chart bar shows how many times more Code, one ↓ chameneos-redux program used, compared to the program that used least Code.
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 | sort | sort | ||||
| × | Program Source Code | CPU secs | Elapsed secs | Memory KB | Code B | ≈ CPU Load |
|---|---|---|---|---|---|---|
| 1.0 | MicroPython #2 | 104.41 | 137.62 | 4,444 | 1191 | 14% 15% 14% 15% 3% 1% 1% 1% |
| 1.0 | Python 3 | 296.43 | 215.33 | 8,728 | 1191 | 19% 14% 14% 13% 14% 15% 14% 14% |
| 1.0 | Python development version | 252.58 | 184.28 | 13,504 | 1191 | 19% 19% 16% 18% 16% 16% 18% 10% |
| 1.0 | Nuitka | 166.14 | 249.97 | 14,700 | 1191 | 10% 9% 8% 8% 7% 5% 6% 6% |
| 1.0 | Python 3 #2 | 5 min | 230.16 | 8,484 | 1191 | 26% 25% 25% 25% 26% 26% 25% 25% |
| 1.0 | Pyston #2 | 151.46 | 230.98 | 14,316 | 1191 | 9% 6% 6% 6% 8% 8% 7% 8% |
| 1.0 | Nuitka #2 | 173.21 | 268.33 | 14,656 | 1191 | 8% 3% 3% 3% 14% 14% 15% 14% |
| 1.0 | RustPython | 220.28 | 215.70 | 15,008 | 1191 | 18% 19% 18% 19% 8% 15% 10% 10% |
| 1.0 | Python development version #2 | 251.45 | 184.80 | 13,484 | 1191 | 20% 21% 16% 23% 13% 17% 12% 10% |
| 1.0 | RustPython #2 | 225.46 | 218.17 | 14,996 | 1191 | 20% 18% 16% 19% 20% 20% 17% 20% |
| 1.0 | MicroPython | 106.40 | 142.47 | 4,340 | 1191 | 13% 11% 10% 10% 11% 9% 9% 9% |
| 1.0 | Cython | 265.20 | 221.39 | 8,232 | 1203 | 6% 9% 7% 6% 8% 7% 10% 8% |
| missing benchmark programs | ||||||
| Python 2 | No program | |||||
| PyPy 2 | No program | |||||
| PyPy 3 | No program | |||||
| Jython | No program | |||||
| IronPython | No program | |||||
| Shedskin | No program | |||||
| Numba | No program | |||||
| Grumpy | No program | |||||
| Graal | No program | |||||
chameneos-redux benchmark : Symmetrical thread rendezvous requests
ndiff program output N = 600 with this output file to check your program output has the correct format before contributing.
We are trying to show the performance of various programming language implementations - so we ask that contributed programs not only give the correct result, but also use the same algorithm to calculate that result.
The text-part and spelled-out numbers in the program output should match the expected output exactly. Thread scheduling may cause small differences in the other numbers, so program output is checked with ndiff -fields 2-10
Each program should
- create differently coloured (blue, red, yellow), differently named, concurrent chameneos creatures
- each creature will repeatedly go to the meeting place and meet, or wait to meet, another chameneos "(at the request the caller does not know whether another chameneos is already present or not, neither if there will be one in some future)"
- both creatures will change colour to complement the colour of the chameneos that they met - don't use arithmetic to complement the colour, use if-else or switch/case or pattern-match
- write all the colour changes for blue red and yellow creatures, using the colour complement function
- for rendezvouses with an odd number of creatures (blue red yellow) and with an even number of creatures (blue red yellow red yellow blue red yellow red blue)
- write the colours the creatures start with
- after N meetings have taken place, for each creature write the number of creatures met and spell out the number of times the creature met a creature with the same name (should be zero)
- spell out the sum of the number of creatures met (should be 2N)
The chameneos benchmark is an adaptation of "Chameneos, a Concurrency Game for Java, Ada and Others" 100KB pdf (which includes example implementations in Java, Ada and C).
Programs may use pre-emptive kernel threads or pre-emptive lightweight threads; but programs that use non pre-emptive threads (coroutines, cooperative threads) and any programs that use custom schedulers, will be listed as interesting alternative implementations. Briefly say what concurrency technique is used in the program header comment.