Mailman 3 - Speed - python.org

pyperformance 0.9.1 released
by Victor Stinner 29 Jul '19

29 Jul '19

Hi, New pyperformance 0.9.1 version fix mako and sqlalchemy benchmarks on Python 3.8 beta2 by upgrading requirements (especially SQLAlchemy and mako). New feature: hg_startup is now run on Python 3! https://pyperformance.readthedocs.io/ https://pyperformance.readthedocs.io/changelog.html Victor -- Night gathers, and now my watch begins. It shall not end until my death.

1 0

Windows PGO+LTO benchmark
by Christoph Reiter 29 Jul '19

29 Jul '19

Hey everyone, I've recently looked into building CPython on Windows with GCC+PGO+LTO and it helped quite a bit with the pyperformance benchmark suite compared to a plain build and compared to the official CPython Windows build, see: https://github.com/msys2/MINGW-packages/pull/5630#issuecomment-514069618 That made me wonder if the official Windows installer uses PGO? If not, maybe it should :)

2 1

speed.python.org must be regenerated
by Victor Stinner 19 Jun '19

19 Jun '19

Hi, For speed.python.org, I run a script manually to "add a new dot" on the graphs. The script always pick the latest versions of pyperf and pyperformance. I also frequently update pyperformance requirements to get security fixes, bug fixes, but also support the latest version of Python: for example, I had multiple issues with Python 3.8. The problem is now that graphs became meaningless because of significant performance changes in dependencies like sympy: https://speed.python.org/timeline/#/?exe=12&ben=sympy_sum&env=1&revs=50&equ… Is there a volunteer to regenerate all data on the latest version of pyperf and pyperformance? It would require to list all commits of previous benchmarks run (it should be as easy a listing the content of a directory, I can tell you more in private), run benchmarks on these commits (I have a script which automate everything), remove old CPython data (but keep PyPy data, who sent it by the way?), and upload new data. Victor -- Night gathers, and now my watch begins. It shall not end until my death.

1 0

benchmarks for python 3.7, 3.8beta
by Matti Picus 06 Jun '19

06 Jun '19

2 1

Rename performance project to pyperformance?
by Victor Stinner 28 May '19

28 May '19

Hi, I just renamed my "perf" module to "pyperf" to avoid confusion with the Linux perf tool which provides a Python binding using "perf" name as well. For the Python benchmark suite https://github.com/python/performance/ I chose to use the "performance" name on GitHub and PyPI, but "pyperformance" on ReadTheDocs to avoid confusion: http://github.com/python/performance/ vs https://pyperformance.readthedocs.io/ Moreover, "pip install performance" installs a program called... "pyperformance" :-) What do you think of renaming "performance" to "pyperformance"? For perf/pyperf, I prefer "pyperf" since pyperf is really designed to measure the perofrmance of Python applications. Same for "performance": it is designed to measure the performance of ... Python itself :-) Victor -- Night gathers, and now my watch begins. It shall not end until my death.

3 4

performance 0.8.0 released
by Victor Stinner 10 May '19

10 May '19

Hi, I just released performance 0.8.0: https://pyperformance.readthedocs.io/ Changes: * compile command: Add "pkg_only" option to benchmark.conf. Add support for native libraries that are installed but not on path. Patch by Robert Grimm. * Update Travis configuration: use trusty image, use pip cache. Patch by Inada Naoki. * Upgrade tornado to 5.1.1. Patch by Inada Naoki. * Fix compile command on Mac OS: no program extension. Patch by Anthony Shaw. * Update requirements: * Chameleon: 3.4 => 3.6.1 * Django: 1.11.16 => 1.11.20 * Genshi: 0.7.1 => 0.7.2 * Mako: 1.0.7 => 1.0.9 * MarkupSafe: 1.0 => 1.1.1 * SQLAlchemy: 1.2.12 => 1.3.3 * certifi: 2018.10.15 => 2019.3.9 * dulwich: 0.19.6 => 0.19.11 * mercurial: 4.7.2 => 5.0 * mpmath: 1.0.0 => 1.1.0 * pathlib2: 2.3.2 => 2.3.3 * perf: 1.5.1 => 1.6.0 * psutil: 5.4.7 => 5.6.2 * six: 1.11.0 => 1.12.0 * sympy: 1.3 => 1.4 * tornado: 4.5.3 => 5.1.1 Victor -- Night gathers, and now my watch begins. It shall not end until my death.

1 0

perf 1.6.0 released
by Victor Stinner 11 Jan '19

11 Jan '19

Changes between 1.5.1 and 1.6.0: * Add *teardown* optional parameter to Runner.timeit() and --teardown option to the "perf timeit" command. Patch by **Alex Khomchenko**. * Runner.timeit(stmt) can now be used to use the statement as the benchmark name. * Port system tune command to Python 2 (use lseek+read/write instead of pread/pwrite which aren't available on Python 2). Patch by **Stefan Talpalaru**. * "perf collect_metadata" now also supports reading CPU frequencies on IBM Z. Victor -- Night gathers, and now my watch begins. It shall not end until my death.

1 0

Call for Abstracts: Modern Language Runtimes, Ecosystems, and VMs (MoreVMs) 2019
by Edd Barrett 11 Dec '18

11 Dec '18

============================================================================ Call for Extended Abstracts: MoreVMs'19 3rd Workshop on Modern Language Runtimes, and Ecosystems Co-located with <Programming>'19 April 1st or 2nd, 2019, Genova, Italy https://2019.programming-conference.org/track/MoreVMs-2019 ============================================================================ Following two previous successful editions, the MoreVMs'19 workshop aims to bring together industrial and academic programmers to discuss the design, implementation, and usage of modern languages and runtimes. This includes aspects such as reuse of language runtimes, modular implementation, language design and compilation strategies. By bringing together both researchers and practitioners, the workshop aims to enable a diverse discussion on how languages and runtimes are currently being utilized, and where they need to improve further. Relevant topics include, but are definitely not limited to, the following: - Extensible VM design (compiler- or interpreter-based VMs) - Reusable components (e.g. interpreters, garbage collectors, ...) - Static and dynamic compilation techniques - Techniques for targeting high-level languages such as JavaScript - Interoperability between languages - Tooling support (e.g. debugging, profiling, etc.) - Programming language development environments - Case studies of existing language implementation approaches - Language implementation challenges and trade-offs - Surveys and usage reports to understand usage in the wild - Ideas for more predictable performance - Ideas for how VMs could take advantage of new hardware features - Ideas for how we should build languages in the future Workshop Format and Submissions ------------------------------- We welcome presentation proposals in the form of extended abstracts (1 to 2 pages long) discussing experiences, work-in-progress, as well as future visions, from either an academic or industrial perspective. The extended abstracts, and if the speakers wish, their slides, will be published on the workshop's web site. Alternatively, the abstracts can be published as part of the companion of <Programming>'19 in the ACM DL. Publication in the ACM DL is conditional on the acceptance by the program committee. Please note that MoreVMs'19 is organized as an academic workshop, and as such, speakers will be required to register for the workshop. Author Instructions ------------------- Submissions should use the ACM Conference 'acmart' Format with the 'sigconf' option and with a font size of 9 point and the font family Libertine/Biolinum. All submissions should be in PDF format. If you use LaTeX or Word, please use the provided ACM acmart templates. Otherwise, please follow the ACM author instructions. If you are formatting your paper using Word, you may wish to use the provided Word template that supports this font size. Please include page numbers in your submission for review using the LaTeX command '\settopmatter{printfolios=true}' (see examples in template). Please also ensure that your submission is legible when printed on a black and white printer. In particular, please check that colors remain distinct and font sizes are legible. Submission Site: https://easychair.org/conferences/?conf=morevms19 Important Dates --------------- Extended abstract submissions: 2019-01-11 Author notification: 2019-02-10 Camera Ready: 2019-02-22 Workshop: 2019-04-01 or 2019-04-02 All deadlines are Anywhere on Earth (AoE), i.e. GMT/UTC-12:00 hour. Program Committee ----------------- Nicolas B. Pierron, Mozilla, France Walter Binder, University of Lugano, Switzerland Eduard-Mihai Burtescu, Lyken Software Solutions Vyacheslav Egorov, Google, Denmark Tony Hosking, Australian National University / Data61, Australia Christoph Kirsch, University of Salzburg, Austria Lun Liu, University of California at Los Angeles, USA Fabio Niephaus, Hasso Plattner Institute, Germany Luís Pina, George Mason University, USA Manuel Rigger, Johannes Kepler University Linz, Austria Jennifer B. Sartor, Ghent University, Belgium Andy Wingo, Igalia, S.L., France Organizers ---------- Edd Barrett, King's College London, UK Stefan Marr, University of Kent, UK Adam Welc, Uber Technologies, USA

1 0

Re: [Speed] http://speed.python.org/ updated manually
by Matti Picus 07 Dec '18

07 Dec '18

2 2

Benchmark Alpine Linux, Debian Stretch and "Slim"
by Victor Stinner 06 Nov '18

06 Nov '18

Hi, I have been told about a benchmark comparing 3 Linux distributions. It runs pyperformance on docker containers. Benchmark: https://github.com/tao12345666333/docker-python-perf Results: http://moelove.info/docker-python-perf/ Victor

1 0