[pypy-svn] r58233 - pypy/extradoc/talk/maemo-summit-2008

[hpk at codespeak.net]

Author: hpk
Date: Fri Sep 19 08:17:36 2008
New Revision: 58233

Modified:
   pypy/extradoc/talk/maemo-summit-2008/lightning.txt
Log:
trying to complete slides for today


Modified: pypy/extradoc/talk/maemo-summit-2008/lightning.txt
==============================================================================
--- pypy/extradoc/talk/maemo-summit-2008/lightning.txt	(original)
+++ pypy/extradoc/talk/maemo-summit-2008/lightning.txt	Fri Sep 19 08:17:36 2008
@@ -1,37 +1,94 @@
-Why yet another python interpreter?
+================================
+PyPy Python on Maemo 
+================================
+
+What is PyPy? 
 ===================================
 
-* PyPy - very compatible to CPython
+* Python Interpreter written in (R)Python 
+
+* framework for implementing dynamic languages
+
+* goal: new deal on flexibility and speed 
+
+Why yet another Python interpreter?
+===================================
+
+* single source translated to C/LLVM/JVM/.NET 
+
+* highly compatible to CPython
 
-* Interpreter written in a static subset of Python
+* super-fast JIT Compilation (in-progress)
 
-* Waaaay easier to experiment with
+* metaprogramming: Waaaay easier to experiment with
 
-Interpreter startup time
+* sandboxing, transparent proxies, ... 
+
+PyPy-c on Maemo / expectations 
+=====================================
+
+* faster startup time (starts from image)
+* Less per-object memory overhead (new GCs)
+* more robust (built-in)
+* high potential for optimizations 
+* run multiple Pythons efficiently 
+* but: slower (0.8-4) for now
+* but: higher interpreter base size for now
+
+PyPy-c on Maemo / status
 ========================
 
-XXX
+* working on benchmarking memory and startup time
+* working on cross-compilation (scratchbox)
+* first pypy-c starts up on device 
+* plan for next months: 
+  * fully working pypy-c/maemo 
+  * extensive benchmarking
+  * some optimizations, maybe new GC 
 
-Memory usage
-============
+Garbage Collectors 
+========================
 
-* Pluggable garbage collectors - why not come with something
-  embedded friendly?
+* PyPy has pluggable garbage collectors 
 
-* Less per-object overhead
+* why not come up with something embedded friendly?
 
 * Impossible in CPython optimizations
 
+* reusable for other language implementations! 
+
+JIT
+===
+
+* In progress for x86
+
+* Why not run on ARM as well?
+
+* speed/memory tradeoffs ?!
+
 Multiple interpreters
 =====================
 
+* goal: run multiple Python processes efficiently 
+
 * Again, pluggable GCs
 
 * Share some static data (pyc files, modules, etc.)
 
-JIT
-===
+Contact / Q&A 
+==========================
 
-* In progress for x86
+holger krekel, Maciej Fijalkowski
+at http://merlinux.eu
 
-* Why not run on ARM as well?
+PyPy: http://codespeak.net/pypy
+
+Blog: http://morepypy.blogspot.com
+
+.. raw:: latex
+
+    \begin{figure}
+    \includegraphics[width=64px,height=64px]{merlinux-logo.jpg}
+    \qquad
+    \includegraphics[width=80px]{../../img/py-web.png}
+    \end{figure}