Author: Matti Picus <matti.pi...@gmail.com> Branch: extradoc Changeset: r5644:90f043cebe19 Date: 2016-07-01 14:53 +0300 http://bitbucket.org/pypy/extradoc/changeset/90f043cebe19/
Log: rewording diff --git a/talk/compiler-workshop-2016/pypy.rst b/talk/compiler-workshop-2016/pypy.rst --- a/talk/compiler-workshop-2016/pypy.rst +++ b/talk/compiler-workshop-2016/pypy.rst @@ -7,7 +7,7 @@ ----------------- PyPy is a mature production-ready framework automatically speeding up pure -python code by factors of 2-5 in commercial settings. +python code by factors of 2-5, already used in commercial settings. The PyPy community offers several tools to inspect and optimize Python programs. Examples: vmprof, cffi @@ -29,8 +29,8 @@ Flow graphs -> Annotation -> RTyping -> Code generation Advantages: -* Whole program optimizations (take that C) -* Deliver features fast, without sacrificing speed +* Whole program optimizations (take that, C) +* Deliver features quickly, without sacrificing speed * Loosely coupled (JIT, Interp., RPython) Downsides: @@ -44,23 +44,24 @@ under-funded. For instance, we could be doing alot more for data science but are moving slowly forward on a volunteer basis with C-API compatibility. -Our interests lie in still providing the confort of the Python eco system, -but not sacrificing execution time. Some details (e.g. garbage collection scheme) +Our interests lie in still providing the comfort of the Python ecosystem, +without sacrificing execution time. Some details (e.g. garbage collection scheme) have some impact on user programs. We could use a lot more help in identifying and resolving -some of these issues. If programs do not run out of the box, most users will stick to CPython -because their performance problems are not that of an issue (at that point in time). +these issues. If programs do not run out of the box, most users will just stick to CPython +because their performance problems are not that big of an issue (at that point in time). If we could resolve those issues (funded, or externally contributed) we would create a much better user experience. We are also working on Micro NumPy, which provides the kernels for numerical operations. -It is very much complete, but still some features are missing. We would love to have a +It is very usable, but still some features are missing. We would love to have a partner/company that would help us to complete NumPy for PyPy. We are open to changes to our JIT scheme. We are working on both high level optimizations and backend oriented changes. Ideas would be to mitigate some issues with our tracing JIT compiler -(or even build a region based compiler) and many more. Most of these aspects are covered quite well by -our core development team, but we will eventually take another big step in near future towards the 7th version -of our JIT. +(or even build a region based compiler) and many more. Most of these aspects are covered +quite well by +our core development team, but we will eventually take another big step in near +future towards the 7th version of our JIT. Other Interesting Aspects ------------------------- _______________________________________________ pypy-commit mailing list pypy-commit@python.org https://mail.python.org/mailman/listinfo/pypy-commit
