BERJAYA

How can I integrate pyperf[ormance] w/ a heavy-duty memory profiler?
by Christos P. Lamprakos Feb. 8, 2022

Feb. 8, 2022

Hi there, I apologize in advance for any potential dumbness in my question. bytehound <https://github.com/koute/bytehound> is a cool profiler that works like this: |$ export MEMORY_PROFILER_LOG=warn $ LD_PRELOAD=./libbytehound.so ./your_application | || What I'm after is to plug it in every run of the benchmarks in pyperformance <https://github.com/python/pyperformance>. It seems like the steps to achieve this are: 1. Fork pyperf <https://github.com/psf/pyperf>, since it is the actual benchmark-running engine. 2. Modify pyperf so as to make command prepending possible somehow. 3. Install this modified pyperf. 4. Install pyperformance on top of the modified pyperf. I do not have the knowledge or experience to tackle step 2 on my own. Could I have your opinion on the whole endeavor, and maybe some advice? Thanks a lot, Christos Lamprakos || ||||

2 3

MoreVMs 2022 : Workshop on Modern Language Runtimes, Ecosystems, and VMs
by Rodrigo Bruno Jan. 18, 2022

Jan. 18, 2022

====================================================================== Call for Extended Abstracts and Talks: MoreVMs’22 6th Workshop on Modern Language Runtimes, Ecosystems, and VMs Co-located with ‹Programming›’22 March 22nd, 2022, Porto, Portugal https://2022.programming-conference.org/home/MoreVMs-2022#Call-for-Talks-an… ====================================================================== Following six previous successful editions, the MoreVMs’22 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. In addition to conventional workshop-style submissions, MoreVMs also accepts (and encourages) submissions that present early-stage work and emerging ideas. 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 (2 to 4 pages long), talk proposals (title and 400 words abstract), and blog posts, discussing new techniques, insights, experiences, works-in-progress, as well as future visions, from either an academic or industrial perspective. The extended abstracts and talk proposals, and if the speakers wish, their slides, will be published on the workshop's website. Alternatively, extended abstracts can be published as part of the companion of ‹Programming›’22 in the ACM DL. Publication in the ACM DL is conditional on the acceptance by the program committee. Please note that MoreVMs’22 is organized as an academic workshop, and as such, speakers will be required to register for the workshop. We regret that we are unable to cover registration, travel, or accommodation costs for authors. Important Dates --------------- Extended abstract and talk submissions: 2022-01-27 Author notification: 2022-02-15 Camera Ready: 2022-03-01 Workshop: 2022-03-22 All deadlines are Anywhere on Earth (AoE), i.e. GMT/UTC-12:00 hour. Organizers ---------- Rodrigo Bruno, INESC-ID / Técnico, ULisboa, Portugal Michael Engel, NTNU, Norway -- rodrigo-bruno.github.io

1 0

Fwd: feedback on: speed.python.org/comparison/
by Christopher Brousseau Oct. 7, 2021

Oct. 7, 2021

Forwarding this feedback on speed.python.org/comparison/ to the right mailing list this time (thx Victor). Speed team -- thanks for your great work, please see email below for some minor comments on the speed.python.org/comparison page. Let me know if there is anything else I can do to help Chris Christopher Brousseau Founder & CEO surfaceOwl.com <https://www.surfaceOwl.com> ---------- Forwarded message --------- From: Christopher Brousseau <chris(a)surfaceowl.com> Date: Tue, Oct 5, 2021 at 9:37 AM Subject: feedback on: speed.python.org/comparison/ To: <speed-owner(a)python.org> Great project - thank you for doing this. I love the new speed results for 3.10 so quickly. *Regarding the comparison page on the website -- two items for your consideration:* *1. One Python release is out of order. * I just noticed that on this tab, the in the list of Python releases - 3.8 should be after 3.7... (see below). Impact is it is more difficult to see performance changes between multiple versions (see attached graphic). CPython <https://speed.python.org/comparison/#>(All <https://speed.python.org/comparison/#>, None) <https://speed.python.org/comparison/#> - lto-pgo latest in branch '3.6' - lto-pgo latest in branch '3.8' - lto-pgo latest in branch '3.7' - lto-pgo latest in branch '3.9' - lto-pgo latest in branch 'master' - lto-pgo latest in branch '3.10' PyPy <https://speed.python.org/comparison/#>(All <https://speed.python.org/comparison/#>, None) <https://speed.python.org/comparison/#> *2. Comparison charts layout could be improved - legend overlays main graph. * Currently I'm seeing the legend of benchmarks overlaid directly on top of the cumulative performance graph (see same attached graphic). This happens for me on both Firefox 92.0.1 and Chrome 94.0.somebignumber; both on Windows 10. Thanks again for your service here - great stuff. Chris Christopher Brousseau Founder & CEO surfaceOwl.com <https://www.surfaceOwl.com>

2 1

Benchmarks not running after "main" branch rename.
by Dennis Sweeney May 10, 2021

May 10, 2021

It looks like speed.python.org has no benchmarks from after May 3. I suspect this is because that is the date when CPython's default branch was renamed to "main". Does someone know how to fix this? I am particularly interested in the effects of Mark Shannon's Zero-Cost Exception Handling commit here: https://github.com/python/cpython/pull/25729 . Thanks, Dennis

2 1

pyperf 2.1.0 released
by Victor Stinner Jan. 14, 2021

Jan. 14, 2021

Hi, I released pyperf 2.1.0: the compare_to command now computes the geometric mean of a whole benchmark suite and no longer displays percentages (display less number to not confuse readers). If the benchmark suites contain more than one benchmark, the geometric mean is computed: normalize benchmark results means to the reference results means. For comparisons, pyperf only displays numbers greater than or equal to 1.0 but mentions "faster" or "slower". speed.pypy.org displays the geometric *both* ways: "The geometric average of all benchmarks is 0.23 or 4.3 times faster than cpython." I prefer to only displays a single number, so I picked "4.3x faster" rather than "0.23 (faster)". Example: $ python3 -m pyperf compare_to --table mult_list_py36.json mult_list_py37.json mult_list_py38.json +----------------+----------------+-----------------------+-----------------------+ | Benchmark | mult_list_py36 | mult_list_py37 | mult_list_py38 | +================+================+=======================+=======================+ | [1]*1000 | 2.13 us | 2.09 us: 1.02x faster | not significant | +----------------+----------------+-----------------------+-----------------------+ | [1,2]*1000 | 3.70 us | 5.28 us: 1.42x slower | 3.18 us: 1.16x faster | +----------------+----------------+-----------------------+-----------------------+ | [1,2,3]*1000 | 4.61 us | 6.05 us: 1.31x slower | 4.17 us: 1.11x faster | +----------------+----------------+-----------------------+-----------------------+ | Geometric mean | (ref) | 1.22x slower | 1.09x faster | +----------------+----------------+-----------------------+-----------------------+ Here you can see that Python 3.7 is faster than Python 3.6 on one benchmark, but slower on two benchmarks. What does it mean? Is it slower or faster "overall"? The geometric mean "1.22x slower" helps to quickly see that Python 3.7 is overall slower. Python 3.8 is faster than Python 3.6 on two benchmarks and one benchmark is not significant. The geometric mean "1.09x faster" confirms that it's faster, but it also tells how much "overall". The geometric mean gives the same weight (1.0) to all benchmarks. It's up to you to carefully check the benchmarks that you consider as the most important, and not only rely on the geometric mean. See also compare_to documentation for more details: https://pyperf.readthedocs.io/en/latest/cli.html#compare-to-cmd Victor -- Night gathers, and now my watch begins. It shall not end until my death.

1 0

New geometric mean feature in pyperf compare_to command
by Victor Stinner Oct. 27, 2020

Oct. 27, 2020

Hi, I implemented a new feature in the pyperf compare_to command: compute the geometric mean of the benchmarks values mean normalized to the reference benchmark suite. Before making a release, I'm looking for testers and feedback to ensure that I implemented it properly and makes sure that it's useful and relevant. You can test using these commands: --- git clone https://github.com/psf/pyperf/ cd pyperf python3 -m pyperf compare_to ref.json my_change.json --- Example of the new feature: $ python3 -m pyperf compare_to ./pyperf/tests/mult_list_py36.json ./pyperf/tests/mult_list_py37.json [1]*1000: Mean +- std dev: [mult_list_py36] 2.13 us +- 0.06 us -> [mult_list_py37] 2.09 us +- 0.04 us: 1.02x faster (-2%) [1,2]*1000: Mean +- std dev: [mult_list_py36] 3.70 us +- 0.05 us -> [mult_list_py37] 5.28 us +- 0.09 us: 1.42x slower (+42%) [1,2,3]*1000: Mean +- std dev: [mult_list_py36] 4.61 us +- 0.13 us -> [mult_list_py37] 6.05 us +- 0.11 us: 1.31x slower (+31%) Geometric mean: 1.22 (slower) $ python3 -m pyperf compare_to ./pyperf/tests/mult_list_py36.json ./pyperf/tests/mult_list_py37.json -G Slower (2): - [1,2]*1000: 3.70 us +- 0.05 us -> 5.28 us +- 0.09 us: 1.42x slower (+42%) - [1,2,3]*1000: 4.61 us +- 0.13 us -> 6.05 us +- 0.11 us: 1.31x slower (+31%) Faster (1): - [1]*1000: 2.13 us +- 0.06 us -> 2.09 us +- 0.04 us: 1.02x faster (-2%) Geometric mean: 1.22 (slower) $ python3 -m pyperf compare_to ./pyperf/tests/mult_list_py36.json ./pyperf/tests/mult_list_py37.json --table +----------------+----------------+------------------------------+ | Benchmark | mult_list_py36 | mult_list_py37 | +================+================+==============================+ | [1]*1000 | 2.13 us | 2.09 us: 1.02x faster (-2%) | +----------------+----------------+------------------------------+ | [1,2]*1000 | 3.70 us | 5.28 us: 1.42x slower (+42%) | +----------------+----------------+------------------------------+ | [1,2,3]*1000 | 4.61 us | 6.05 us: 1.31x slower (+31%) | +----------------+----------------+------------------------------+ | Geometric mean | (ref) | 1.22 (slower) | +----------------+----------------+------------------------------+ $ python3 -m pyperf compare_to ./pyperf/tests/mult_list_py36.json ./pyperf/tests/mult_list_py37.json --table -G +----------------+----------------+------------------------------+ | Benchmark | mult_list_py36 | mult_list_py37 | +================+================+==============================+ | [1]*1000 | 2.13 us | 2.09 us: 1.02x faster (-2%) | +----------------+----------------+------------------------------+ | [1,2,3]*1000 | 4.61 us | 6.05 us: 1.31x slower (+31%) | +----------------+----------------+------------------------------+ | [1,2]*1000 | 3.70 us | 5.28 us: 1.42x slower (+42%) | +----------------+----------------+------------------------------+ | Geometric mean | (ref) | 1.22 (slower) | +----------------+----------------+------------------------------+ Victor -- Night gathers, and now my watch begins. It shall not end until my death.

1 0

Pyperformance and -DDYNAMIC_EXECUTION_PROFILE
by Skip Montanaro March 29, 2020

March 29, 2020

I'm interested in some dynamic execution counts (sys.getdxp). I have a Python executable built with that. The recommended way to capture execution profiles is to run the desired program with -i and use that to grab and write the opcode profile. That would be quite cumbersome when using pyperformance since each benchmark is run as a separate Python process and there are so many benchmarks. Is there some builtin way to save the output of sys.getdxp() after each benchmark is run? If not, is there an approach to that I should consider, perhaps a plug-in capability I missed in a quick skim of the docs? Thanks, Skip Montanaro

1 1

pyperf 1.7.0 and pyperformance 1.0.0 released
by Victor Stinner Dec. 17, 2019

Dec. 17, 2019

Hi, I released pyperf 1.7.0 and pyperformance 1.0.0. The major change is that pyperformance 1.0 dropped Python 2 support. pyperformance changes between 0.9.1 and 1.0.0: * Enable pyflate benchmarks on Python 3. * Remove ``spambayes`` benchmark: it is not compatible with Python 3. * Remove ``2n3``:benchmark group. * Drop Python 2.7 support: old Django and Tornado versions are not compatible with incoming Python 3.9. * Disable html5lib benchmark temporarily, since it's no longer compatible with Python 3.9. * Update requirements: * Django: 1.11.22 => 3.0 * Mako: 1.0.14 => 1.1.0 * SQLAlchemy: 1.3.6 => 1.3.12 * certifi: 2019.6.16 => 2019.11.28 * docutils: 0.15.1 => 0.15.2 * dulwich: 0.19.11 => 0.19.14 * mercurial: 5.0.2 => 5.1.1 * psutil: 5.6. => 5.6.7 * pyperf: 1.6.1 => 1.7.0 * six: 1.12. => 1.13.0 * sympy: 1.4 => 1.5 pyperf changes between 1.6.1 to 1.7.0: * metadata: add ``python_compiler`` * Windows: inherit ``SystemDrive`` environment variable by default. Contribution by Steve Dower. * Fix tests on ARM and PPC: cpu_model_name metadata is no longer required on Linux. * tests: Do not allow test suite to execute without unittest2 on Python2, otherwise man failures occur due to missing 'assertRegex'. Contribution by John Vandenberg. * doc: Update old/dead links. * Travis CI: drop Python 3.4 support. I'm working with Pablo Galindo to recompute all benchmarks on speed.python.org with these new versions. Previously, I always upgraded pyperf and pyperformance using git: I always ran the master branch of these projects. The problem is that when a dependency is upgrade (like Django), we don't know if the performance changed between of Python or the dependency. We will keep you in touch on the progress of this task. Old results are archived at: https://github.com/vstinner/performance_results/tree/master/2019-12-17-cpyt… Victor -- Night gathers, and now my watch begins. It shall not end until my death.

1 0

pyperformance drops Python 2.7 support
by Victor Stinner Dec. 17, 2019

Dec. 17, 2019

Hi, Python 3.9 introduced incompatible changes which broke Django and Tornado benchmarks of pyperformance. But Python 2.7 support prevented me to upgrade Django and Tornado which were stuck to Django 1.11.x and Tornado 5.x. I decided to drop Python 2.7 support in pyperformance to support Python 3.9. So I was able to upgrade to Django 3.x and Tornado 6.x. PyPy is still supported but only PyPy3 (basic support, no benchmark is adjusted for PyPy JIT compiler). So if you want to compare Python 2 to Python 3, you will be limited to pyperformance 0.9.1 which supports Python 2.7 and Python 3.8. Victor -- Night gathers, and now my watch begins. It shall not end until my death.

1 0

Python 3.8 compared to Python 3.7
by Victor Stinner Oct. 10, 2019

Oct. 10, 2019

I have been asked to update speed.python.org, so here are some data. I didn't look into the details. Python 3.8 compared to 3.7 (compare development branches): At least 10% difference: 10 faster, 3 slower haypo@speed-python$ PYTHONPATH=~/pyperf python3 -m pyperf compare_to /home/haypo/json/uploaded/2019-10-10_11-17-3.7-ca012360b103.json.gz /home/haypo/json/uploaded/2019-10-10_11-19-3.8-baf8a9b03a56.json.gz -G --min-speed=10 --table +-----------------------+-----------------------------------+-----------------------------------+ | Benchmark | 2019-10-10_11-17-3.7-ca012360b103 | 2019-10-10_11-19-3.8-baf8a9b03a56 | +=======================+===================================+===================================+ | sympy_expand | 1.07 sec | 843 ms: 1.27x faster (-22%) | +-----------------------+-----------------------------------+-----------------------------------+ | sympy_integrate | 45.6 ms | 37.1 ms: 1.23x faster (-19%) | +-----------------------+-----------------------------------+-----------------------------------+ | sympy_str | 651 ms | 540 ms: 1.21x faster (-17%) | +-----------------------+-----------------------------------+-----------------------------------+ | pickle_dict | 55.4 us | 46.3 us: 1.20x faster (-16%) | +-----------------------+-----------------------------------+-----------------------------------+ | unpickle_pure_python | 726 us | 618 us: 1.18x faster (-15%) | +-----------------------+-----------------------------------+-----------------------------------+ | sympy_sum | 369 ms | 315 ms: 1.17x faster (-15%) | +-----------------------+-----------------------------------+-----------------------------------+ | sqlalchemy_imperative | 73.0 ms | 64.3 ms: 1.14x faster (-12%) | +-----------------------+-----------------------------------+-----------------------------------+ | pickle | 23.1 us | 20.3 us: 1.14x faster (-12%) | +-----------------------+-----------------------------------+-----------------------------------+ | mako | 31.6 ms | 28.2 ms: 1.12x faster (-11%) | +-----------------------+-----------------------------------+-----------------------------------+ | django_template | 292 ms | 264 ms: 1.11x faster (-10%) | +-----------------------+-----------------------------------+-----------------------------------+ | nbody | 234 ms | 266 ms: 1.14x slower (+14%) | +-----------------------+-----------------------------------+-----------------------------------+ | scimark_fft | 640 ms | 730 ms: 1.14x slower (+14%) | +-----------------------+-----------------------------------+-----------------------------------+ | logging_silent | 316 ns | 391 ns: 1.24x slower (+24%) | +-----------------------+-----------------------------------+-----------------------------------+ More verbose, at least 5% difference: haypo@speed-python$ PYTHONPATH=~/pyperf python3 -m pyperf compare_to /home/haypo/json/uploaded/2019-10-10_11-17-3.7-ca012360b103.json.gz /home/haypo/json/uploaded/2019-10-10_11-19-3.8-baf8a9b03a56.json.gz -G --min-speed=5 --table +-------------------------+-----------------------------------+-----------------------------------+ | Benchmark | 2019-10-10_11-17-3.7-ca012360b103 | 2019-10-10_11-19-3.8-baf8a9b03a56 | +=========================+===================================+===================================+ | sympy_expand | 1.07 sec | 843 ms: 1.27x faster (-22%) | +-------------------------+-----------------------------------+-----------------------------------+ | sympy_integrate | 45.6 ms | 37.1 ms: 1.23x faster (-19%) | +-------------------------+-----------------------------------+-----------------------------------+ | sympy_str | 651 ms | 540 ms: 1.21x faster (-17%) | +-------------------------+-----------------------------------+-----------------------------------+ | pickle_dict | 55.4 us | 46.3 us: 1.20x faster (-16%) | +-------------------------+-----------------------------------+-----------------------------------+ | unpickle_pure_python | 726 us | 618 us: 1.18x faster (-15%) | +-------------------------+-----------------------------------+-----------------------------------+ | sympy_sum | 369 ms | 315 ms: 1.17x faster (-15%) | +-------------------------+-----------------------------------+-----------------------------------+ | sqlalchemy_imperative | 73.0 ms | 64.3 ms: 1.14x faster (-12%) | +-------------------------+-----------------------------------+-----------------------------------+ | pickle | 23.1 us | 20.3 us: 1.14x faster (-12%) | +-------------------------+-----------------------------------+-----------------------------------+ | mako | 31.6 ms | 28.2 ms: 1.12x faster (-11%) | +-------------------------+-----------------------------------+-----------------------------------+ | django_template | 292 ms | 264 ms: 1.11x faster (-10%) | +-------------------------+-----------------------------------+-----------------------------------+ | dulwich_log | 155 ms | 145 ms: 1.07x faster (-7%) | +-------------------------+-----------------------------------+-----------------------------------+ | regex_compile | 364 ms | 340 ms: 1.07x faster (-6%) | +-------------------------+-----------------------------------+-----------------------------------+ | xml_etree_iterparse | 189 ms | 178 ms: 1.06x faster (-5%) | +-------------------------+-----------------------------------+-----------------------------------+ | pickle_list | 7.24 us | 6.85 us: 1.06x faster (-5%) | +-------------------------+-----------------------------------+-----------------------------------+ | regex_effbot | 5.10 ms | 4.85 ms: 1.05x faster (-5%) | +-------------------------+-----------------------------------+-----------------------------------+ | scimark_monte_carlo | 200 ms | 211 ms: 1.05x slower (+5%) | +-------------------------+-----------------------------------+-----------------------------------+ | fannkuch | 883 ms | 932 ms: 1.06x slower (+6%) | +-------------------------+-----------------------------------+-----------------------------------+ | pyflate | 1.30 sec | 1.38 sec: 1.06x slower (+6%) | +-------------------------+-----------------------------------+-----------------------------------+ | chameleon | 20.9 ms | 22.2 ms: 1.06x slower (+6%) | +-------------------------+-----------------------------------+-----------------------------------+ | python_startup | 11.5 ms | 12.3 ms: 1.07x slower (+7%) | +-------------------------+-----------------------------------+-----------------------------------+ | spectral_norm | 247 ms | 265 ms: 1.07x slower (+7%) | +-------------------------+-----------------------------------+-----------------------------------+ | unpack_sequence | 114 ns | 122 ns: 1.08x slower (+8%) | +-------------------------+-----------------------------------+-----------------------------------+ | pickle_pure_python | 934 us | 1.02 ms: 1.09x slower (+9%) | +-------------------------+-----------------------------------+-----------------------------------+ | regex_dna | 271 ms | 295 ms: 1.09x slower (+9%) | +-------------------------+-----------------------------------+-----------------------------------+ | scimark_sparse_mat_mult | 8.61 ms | 9.38 ms: 1.09x slower (+9%) | +-------------------------+-----------------------------------+-----------------------------------+ | nbody | 234 ms | 266 ms: 1.14x slower (+14%) | +-------------------------+-----------------------------------+-----------------------------------+ | scimark_fft | 640 ms | 730 ms: 1.14x slower (+14%) | +-------------------------+-----------------------------------+-----------------------------------+ | logging_silent | 316 ns | 391 ns: 1.24x slower (+24%) | +-------------------------+-----------------------------------+-----------------------------------+ Victor -- Night gathers, and now my watch begins. It shall not end until my death.

1 0