[pypy-commit] extradoc extradoc: work on slides
fijal
noreply at buildbot.pypy.org
Mon Feb 20 23:29:33 CET 2012
Author: Maciej Fijalkowski <fijall at gmail.com>
Branch: extradoc
Changeset: r4091:47da3b7e55c1
Date: 2012-02-19 20:08 +0200
http://bitbucket.org/pypy/extradoc/changeset/47da3b7e55c1/
Log: work on slides
diff --git a/talk/sea2012/talk.rst b/talk/sea2012/talk.rst
--- a/talk/sea2012/talk.rst
+++ b/talk/sea2012/talk.rst
@@ -4,13 +4,13 @@
What is this talk about?
------------------------
-* what is pypy and why
+* What is PyPy and why?
-* numeric landscape in python
+* Numeric landscape in python
-* what we achieved in pypy
+* What we achieved in PyPy?
-* where we're going
+* Where we're going?
What is PyPy?
-------------
@@ -26,7 +26,7 @@
PyPy status right now
---------------------
-* An efficient just in time compiler for the Python language
+* An **efficient just in time compiler** for the Python language
* Relatively "good" on numerics (compared to other dynamic languages)
@@ -37,7 +37,7 @@
Why would you care?
-------------------
-* "If I write this stuff in C it'll be faster anyway"
+* "If I write this stuff in C/fortran/assembler it'll be faster anyway"
* maybe, but ...
@@ -50,7 +50,33 @@
* For novel algorithms, being clearly expressed in code makes them easier to evaluate (Python is cleaner than C often)
-* Example - memcached server (?) XXX think about it
+Why would you care even more
+----------------------------
+
+* Growing community
+
+* Everything is for free with reasonable licensing
+
+* There are many smart people out there addressing hard problems
+
+Example why would you care
+--------------------------
+
+* You spend a year writing optimized algorithms for a GPU
+
+* Next year a new generation of GPUs come along
+
+* Your algorithms are no longer optimize
+
+|pause|
+
+* Alternative - express your algorithms
+
+* Leave low-level details for people who have nothing better to do
+
+|pause|
+
+* Like me (I don't know enough physics to do the other part)
Numerics in Python
------------------
@@ -113,7 +139,7 @@
Examples
--------
-XXX say that the variables are e.g. 1-dim numpy arrays
+* ``a``, ``b``, ``c`` are single dimensional arrays
* ``a + a`` would generate different code than ``a + b``
@@ -130,19 +156,55 @@
* Vectorization in progress
-Status benchmarks
------------------
+Status benchmarks - trivial stuff
+---------------------------------
+
+XXX
+
+Status benchmarks - slightly more complex
+-----------------------------------------
* laplace solution
* solutions:
+ XXX laplace numbers
+---+
| |
+---+
+Progress plan
+-------------
+
+* Express operations in high-level languages
+
+* Let us deal with low level details
+
+|pause|
+
+* However, leave knobs and buttons for advanced users
+
+* Don't get penalized too much for not using them
+
+Few words about the future
+--------------------------
+
+* Predictions are hard
+
+|pause|
+
+* Especially when it comes to future
+
+* Take this with a grain of salt
+
This is just the beginning...
-----------------------------
* PyPy is an easy platform to experiment with
+* We did not spend a whole lot of time dealing with the low-level optimizations
+
+Extra - SSE preliminary results
+-------------------------------
+
+XXX
More information about the pypy-commit
mailing list