[pypy-commit] extradoc extradoc: my pycon abstract

[fijal]

Author: Maciej Fijalkowski <fijall at gmail.com>
Branch: extradoc
Changeset: r4831:a75bf0b51508
Date: 2012-09-28 12:58 +0200
http://bitbucket.org/pypy/extradoc/changeset/a75bf0b51508/

Log:	my pycon abstract

diff --git a/talk/pycon2013/abstract_fijal.rst b/talk/pycon2013/abstract_fijal.rst
new file mode 100644
--- /dev/null
+++ b/talk/pycon2013/abstract_fijal.rst
@@ -0,0 +1,23 @@
+Speeding up existing code using PyPy
+====================================
+
+Brief outline:
+
+I spent quite some time profiling existing python programs under PyPy.
+This talk will walk through an existing Python library (undecided which yet)
+and showcase how to write benchmarks, how to find bottlenecks, how to analyze
+them and how to improve them when running on the PyPy interpreter and what
+are the theoretical and pracitcal limits.
+
+Detailed abstract:
+
+In this talk I would like to share my experience when optimizing existing
+Python codebases. I spend copious amounts of time staring at profiling data,
+improving profilers to see anything and improving PyPy to work better
+on real-life workloads. I would like to give the audience insight what
+sort of constructs are optimized by PyPy, what sort of constructs can
+possibly be optimized and which ones are out of question. This talk is
+an intermediate one and assumes good enough knowledge of Python to understand
+code of a given library (Twisted, Django, Flask, Gunicorn and some stdlib
+module are potential candidates), however no prior knowledge of PyPy or
+the processor performance characteristics is necessary.