Speculative Staging for Interpreter Optimization · HackerPapers discussions

Speculative Staging for Interpreter Optimization — mentioned by gergo_barany

Fri, 18 May 2018 12:13:41 GMT

> Is that because Python already is the way it is? Partly, yes. But also because the optimizations I would have come up with were all tried by Stefan Brunthaler before. See some citations in the paper, in particular to: http://arxiv.org/abs/1310.2300 where he claims a 4x speedup over CPython using purely interpreter-based and safe optimizations. So I guess I should have written "no really obvious and new optimizations to try". Anyway, Stefan's work in general is very interesting for implementors of dynamic language interpreters. A lot of it harks back to things that were first developed for…

Paper and discussion history. A mention is not an endorsement.

Speculative Staging for Interpreter Optimization — mentioned by gergo_barany

Wed, 07 Feb 2018 15:24:02 GMT

> Where are the main blowouts in python performance? I did some research a few years ago that tried to quantify some of this. If you trust my methodology, the biggest problems (depending on application, of course) are: boxing of numbers; list/array indexing with boxed numbers and bounds checking; and late binding of method calls. Basically, doing arithmetic on lists of numbers in pure Python is about the worst thing you can do. And it's not just due to dynamic typing: Even if you know that two numbers you want to add are floats, they are still floats stored in boxed form as objects in memory…

Paper and discussion history. A mention is not an endorsement.

Speculative Staging for Interpreter Optimization — HN submission

Thu, 02 Jan 2014 02:11:54 GMT

Speculative Staging for Interpreter Optimization

1 point; 1 discussion reply on HN. Paper and source history. A submission is not an endorsement.