[pypy-svn] r64913 - pypy/extradoc/talk/euroscipy2009
benjamin at codespeak.net
benjamin at codespeak.net
Fri May 1 04:56:27 CEST 2009
Author: benjamin
Date: Fri May 1 04:56:17 2009
New Revision: 64913
Modified:
pypy/extradoc/talk/euroscipy2009/abstract.txt
Log:
edits
Modified: pypy/extradoc/talk/euroscipy2009/abstract.txt
==============================================================================
--- pypy/extradoc/talk/euroscipy2009/abstract.txt (original)
+++ pypy/extradoc/talk/euroscipy2009/abstract.txt Fri May 1 04:56:17 2009
@@ -2,22 +2,22 @@
PyPy's JIT and Numpy
====================
-Common problem when developing scientific application is that CPython's
-interpreter is too slow. This can mitigated by usage of FORTRAN, C or Cython
-in performance-critical parts of the code, but it would be much nicer
-to just run python faster.
+A common problem when developing scientific applications is that CPython is
+too slow. This can mitigated by usage of FORTRAN, C, or Cython in
+performance-critical parts of the code, but it would be much nicer if
+python ran faster.
-JIT was one of the main objectives of PyPy project for quite a while now.
-As of `March 2009`_ we're able to speed up simple examples in Python
-for about 20-30x over the speed of CPython. Since PyPy's JIT is much more
-flexible than for example Psyco, we expect even greater speedups in the
-future, as well as support for floats and 64bit architecture, which Psyco
-will not achieve in forseeable future.
+Creating a JIT has been one of the main objectives of the PyPy project for
+quite a while now. As of `March 2009`_, we're able to speed up simple
+examples in Python t about 20-30x over the speed of CPython. Since PyPy's
+JIT is much more flexible than others, Psyco for example, we expect even
+greater speedups in the future, as well as support for floats and 64bit
+architectures, which Psyco will not achieve in forseeable future.
-In this talk we would like to talk about PyPy's JIT, design principles and
-it's future, without going into too many architectural details.
+In this talk, we will talk about the design principles and future of PyPy's
+JIT. We won't go into too many architectural details.
-We would also like to present how JIT can make the life easier of simple
+We will also present how JIT can make the life easier for simple
postprocessing of data generated by EULAG model. XXX extend.
.. _`March 2009`: http://morepypy.blogspot.com/2009/03/good-news-everyone.html
More information about the Pypy-commit
mailing list