Author: Maciej Fijalkowski <fij...@gmail.com> Branch: extradoc Changeset: r4982:c7e44e1cc901 Date: 2013-07-11 11:50 +0200 http://bitbucket.org/pypy/extradoc/changeset/c7e44e1cc901/
Log: update benchmark nos diff --git a/blog/draft/duhton.rst b/blog/draft/duhton.rst --- a/blog/draft/duhton.rst +++ b/blog/draft/duhton.rst @@ -23,7 +23,9 @@ there are no conflicting writes to global memory and hence the demos are very amenable to parallelization. They exercise: -* arithmetics - ``demo/many_sqare_roots.duh`` +* arithmetics - ``demo/many_sqare_roots.duh``:: + + * read-only access to globals - ``demo/trees.duh`` @@ -33,3 +35,30 @@ Duhton can be found in `the stmgc repo`_, while the STM-less Duhton, that uses refcounting, can be found in `the duhton repo`_ under the ``base`` branch. + +Below are some benchmarks. Note that this is a little comparing apples to +oranges since the single-threaded duhton uses refcounting GC vs generational +GC for STM version. Future pypy benchmarks will compare more apples to apples. +Moreover none of the benchmarks has any conflicts. Time is the total time +that the benchmark took (not the CPU time) and there was very little variation +in the consecutive runs (definitely below 5%). + ++-----------+---------------------+----------------+-----------+-----------+ +| benchmark | 1 thread (refcount) | 1 thread (stm) | 2 threads | 4 threads | ++-----------+---------------------+----------------+-----------+-----------+ +| square | 1.9s | 3.5s | 1.8s | 0.9s | ++-----------+---------------------+----------------+-----------+-----------+ +| trees | 0.6s | 1.0s | 0.54s | 0.28s | ++-----------+---------------------+----------------+-----------+-----------+ +| trees2 | 1.4s | 2.2s | 1.1s | 0.57s | ++-----------+---------------------+----------------+-----------+-----------+ + +As you can see, the slowdown for STM vs single thread is significant +(1.8x, 1.7x, 1.6x respectively), but still lower than 2x. However the speedup +from running on multiple threads parallelizes the problem almost perfectly. + +While a significant milestone, we hope the next blog post will cover +STM-enabled pypy that's fully working with JIT work ongoing. + +Cheers, +fijal on behalf of Remi Meier and Armin Rigo _______________________________________________ pypy-commit mailing list pypy-commit@python.org http://mail.python.org/mailman/listinfo/pypy-commit
