Author: Maciej Fijalkowski <[email protected]>
Branch: extradoc
Changeset: r4968:ee64ee05d215
Date: 2013-05-02 19:20 +0200
http://bitbucket.org/pypy/extradoc/changeset/ee64ee05d215/

Log:    work on a draft

diff --git a/blog/draft/pypy-alpha-arm.rst b/blog/draft/pypy-alpha-arm.rst
--- a/blog/draft/pypy-alpha-arm.rst
+++ b/blog/draft/pypy-alpha-arm.rst
@@ -40,10 +40,27 @@
 Benchmarks
 ==========
 
-Everybody loves benchmarks. Here is a table of our benchmark suite (for ARM we 
don't
-provide it yet on http://speed.pypy.org, unfortunately).
+Everybody loves benchmarks. Here is a table of our benchmark suite
+(for ARM we don't provide it yet on http://speed.pypy.org,
+unfortunately).
 
-This is a comparison of Cortex A9 processor with 4M cache and Xeon XXX fill in
+This is a comparison of Cortex A9 processor with 4M cache and Xeon W3580 with
+8M of L3 cache. The set of benchmarks is a subset of what we run for
+http://speed.pypy.org that finishes in reasonable time. The ARM machine
+was provided by Calxeda.
+Columns are respectively:
+
+* benchmark name
+
+* PyPy speedup over CPython on ARM
+
+* PyPy speedup over CPython on x86
+
+* speedup on Xeon vs Cortex A9, as measured on CPython
+
+* speedup on Xeon vs Cortex A9, as measured on PyPy
+
+* relative speedup (how much bigger the x86 speedup is over ARM speedup)
 
 
+--------------------+-----------------------+-----------------------+-------------------+----------------------+------------------+
 | Benchmark          | PyPy vs CPython (arm) | PyPy vs CPython (x86) | x86 vs 
arm (pypy) | x86 vs arm (cpython) | relative speedup |
@@ -111,7 +128,11 @@
 | twisted_pb         | 4.94                  | 3.02                  | 5.10    
          | 8.34                 | 0.61             | 
 
+--------------------+-----------------------+-----------------------+-------------------+----------------------+------------------+
 
-XXX some stuff
+It seems that Cortex A9, while significantly slower than Xeon, has higher
+slowdowns with a large interpreter (CPython) than a JIT compiler (PyPy). This
+comes as a surprise to me, especially that our ARM assembler is not nearly
+as polished as our x86 assembler. As for the causes, various people mentioned
+branch predictor, but I would not like to speculate without actually knowing.
 
 How to use PyPy?
 ================
@@ -125,4 +146,8 @@
 .. _`installation schemes`: 
http://doc.pypy.org/en/latest/getting-started.html#installing-pypy
 .. _`PyPy and pip`: 
http://doc.pypy.org/en/latest/getting-started.html#installing-pypy
 
-XXXX more
+We would not recommend using PyPy on ARM just quite yet, however the day
+of a stable PyPy ARM release is not far off.
+
+Cheers,
+fijal, bivab, arigo and the whole PyPy team
_______________________________________________
pypy-commit mailing list
[email protected]
http://mail.python.org/mailman/listinfo/pypy-commit

Reply via email to