[pypy-svn] r69011 - pypy/extradoc/talk/rupy2009

fijal at codespeak.net fijal at codespeak.net
Thu Nov 5 23:44:44 CET 2009


Author: fijal
Date: Thu Nov  5 23:44:41 2009
New Revision: 69011

Modified:
   pypy/extradoc/talk/rupy2009/talk.pdf
   pypy/extradoc/talk/rupy2009/talk.tex
Log:
update


Modified: pypy/extradoc/talk/rupy2009/talk.pdf
==============================================================================
Files pypy/extradoc/talk/rupy2009/talk.pdf	(original) and pypy/extradoc/talk/rupy2009/talk.pdf	Thu Nov  5 23:44:41 2009 differ

Modified: pypy/extradoc/talk/rupy2009/talk.tex
==============================================================================
--- pypy/extradoc/talk/rupy2009/talk.tex	(original)
+++ pypy/extradoc/talk/rupy2009/talk.tex	Thu Nov  5 23:44:41 2009
@@ -67,7 +67,9 @@
   \begin{itemize}
     \item Python - a programming language
     \item CPython - main implementation of Python
-      xxx
+    \item JVM - Java Virtual Machine - VM used to run Java, among others
+    \item JIT - Just in time compiler
+    \item Psyco - JIT for Python
   \end{itemize}
 \end{frame}
 
@@ -106,7 +108,33 @@
   \pause
   \begin{itemize}
     \item So, it's CPython that is slow on this particular benchmark
+      \pause
+    \item Same example, using numpy and vectorization about 3x faster than JVM
+  \end{itemize}
+\end{frame}
+
+\begin{frame}
+  \frametitle{Python's speed}
+  \begin{itemize}
+    \item Instead of: ``Why is Python slow?''
+      \pause
+    \item Better: ``Why is Python hard to optimize?''
+      \pause
+    \item Even better: ``How are we going to fix it?''
   \end{itemize}
 \end{frame}
 
+\begin{frame}
+  \frametitle{Why is Python hard to optimize?}
+  \begin{itemize}
+    \item Duck typing (dynamic dispatch)
+    \item Frames
+    \item Object encapsulation
+    \item Dictionaries of instances
+  \end{itemize}
+\end{frame}
+
+\begin{frame}
+\end{frame}
+
 \end{document}



More information about the Pypy-commit mailing list