Author: Armin Rigo <ar...@tunes.org> Branch: extradoc Changeset: r4203:076d5ffc08ba Date: 2012-04-27 11:18 +0200 http://bitbucket.org/pypy/extradoc/changeset/076d5ffc08ba/
Log: Clarify and reword. diff --git a/blog/draft/stm-apr2012.rst b/blog/draft/stm-apr2012.rst --- a/blog/draft/stm-apr2012.rst +++ b/blog/draft/stm-apr2012.rst @@ -63,11 +63,13 @@ On a few smaller, more regular examples like richards_, I did measure the performance. It is not great, even taking into account that it has -no JIT so far; but it is well within the 2-to-5-times slower goal, and -it does seem to scale. At least, it scales roughly as expected on my -2-real-cores, 4-hyperthreaded-cores laptop (which means that using two -cores is not quite twice as fast as using only one, and using all four -cores is again not twice faster but only 20-30%). +no JIT so far. Running pypy-stm with one thread is roughly 5 times +slower than running a regular PyPy with no JIT (it used to be better in +previous versions, but they didn't have any GC; nevertheless, I need to +investigate). However, it does seem to scale. At least, it scales +roughly as expected on my 2-real-cores, 4-hyperthreaded-cores laptop +(i.e. for N between 1 and 4, the N-threaded pypy-stm performs similarly +to N independent pypy-stm's running one thread each). And finally... _______________________________________________ pypy-commit mailing list pypy-commit@python.org http://mail.python.org/mailman/listinfo/pypy-commit
