4 ms·
TL;DR - Nuitka (which has been garnering some attention on HN today - https://news.ycombinator.com/item?id=8771925 https://news.ycombinator.com/item?id=8771925)
by mih 12y ago
TL;DR - Nuitka (which has been garnering some attention on HN today - https://news.ycombinator.com/item?id=8771925 https://news.ycombinator.com/item?id=8771925) is not as fast as CPython and less faster than PyPy for the chosen scenario (enumeration of a fat graph and computing their graph homology).
A year and a half down the line after this paper was published (Apr 2013), Nuitka's main strengths seem to be the convenience in packaging the code into an executable which a number of readers have reported success in. If runtime and memory usage are more important, you are better off sticking with the interpreters for now.
- mkesper 12y agoThis should be re-done with up to date versions of all programs. The authors mention having opened bug reports/existing known bugs. All contestants should have time to react to those, shouldn't they?
- reikonomusha 12y agoNot necessarily. A sort of test with a somewhat random computation where implementations have not specifically tuned for said test can provide beneficial information. If you have enough of such tests, one can get a broad idea of the performance of such systems. The worst case is when people hyperoptimize for a particular benchmark, which tells you nothing. You see this especially in the Benchmarks Game.
- andreasvc 12y agoWhile that would be interesting, I don't see it as the responsibility of the author of a conference poster that has already been presented. It would make more sense for the authors of the various Python implementations to take this up as a benchmark.