time-to-botec

Benchmark sampling in different programming languages
Log | Files | Refs | README

commit 72884d8e1e281a1b8b65fd53d0b380c91ae9d8e4
parent 57fc886bed43f11d92438bfa6c44f5f895360077
Author: NunoSempere <nuno.sempere@protonmail.com>
Date:   Thu,  1 Dec 2022 15:37:10 +0000

tweak: clean README, add benchmarks

Diffstat:
MREADME.md | 31+++++++++++++++++++++++--------
1 file changed, 23 insertions(+), 8 deletions(-)

diff --git a/README.md b/README.md @@ -8,21 +8,36 @@ The title of this repository is a pun on two meanings of "time to": "how much ti ## Current languages -- Python -- R -- Squiggle - +- [x] Python +- [x] R +- [x] Squiggle +- [x] Javascript (NodeJS) +- [x] C + +## Performance table + +With the [time](https://man7.org/linux/man-pages/man1/time.1.html) tool, using 1M samples: + +| Language | Time | +|----------|-----------| +| C | 0m0,442s | +| Squiggle | 0m0,488s | +| Node | 0m0,732s | +| R | 0m7,000s | +| Python (CPython) | 0m16,641s | + +I was very surprised that Node/Squiggle code was almost as fast as the raw C code. For the Python code, it's possible that the lack of speed is more a function of me not being as familiar with Python. It's also very possible that the code would run faster with [PyPy](https://doc.pypy.org) + ## Languages I may add later -- Javascript -- Julia +- Julia (TuringML) - Rust -- C +- Lisp - ... and suggestions welcome ## Roadmap -uhe future of this project is uncertain. In most words, I simply forget about this repository. +The future of this project is uncertain. In most words, I simply forget about this repository. ## Other similar projects