asv_bench_memray
This a proof-of-concept externally defined memray benchmark plugin for asv.
Usage
In your asv.conf.json add the following to the requirements matrix:
"matrix": {
"req": {
"numpy": ["1.21"],
"asv_plugin_memray": [""]
},
},
This should be enough for an example like the following to run:
import numpy as np
class MyBenchmark:
params = [10, int(2e4)]
def ray_sum(self, n):
self.data = np.random.rand(n)
np.sum(self.data)
Which should result in something roughly like:
ASV_RUNNER_PATH="../asv_runner" asv run --bench sum
· Creating environments.......
· Discovering benchmarks
·· Uninstalling from virtualenv-py3.9-asv_bench_memray.._asv_bench_memray-numpy1.21
·· Building 30a650cb <main> for virtualenv-py3.9-asv_bench_memray.._asv_bench_memray-numpy1.21.
·· Installing 30a650cb <main> into virtualenv-py3.9-asv_bench_memray.._asv_bench_memray-numpy1.21
· Running 1 total benchmarks (1 commits * 1 environments * 1 benchmarks)
[ 0.00%] · For project commit 30a650cb <main>:
[ 0.00%] ·· Benchmarking virtualenv-py3.9-asv_bench_memray.._asv_bench_memray-numpy1.21
[100.00%] ··· benchmarks.MyBenchmark.ray_sum ok
[100.00%] ··· ======== =======
param1
-------- -------
10 1.72k
20000 162k
======== =======
ASV_RUNNER_PATH="../asv_runner" asv run --bench sum 8.72s user 3.04s system 99% cpu 11.877 total
Development
During development, one needs to pass a relative path:
"matrix": {
"req": {
"asv_bench_memray": ["../asv_bench_memray"]
},
},
Also it may be necessary to cleanup older environments and explicitly point to an instance of asv_runner:
rm -rf .asv && ASV_RUNNER_PATH="../asv_runner" asv run --bench sum
Personally I keep benchmarks for testing at an experiments repo, but any local test will do.
Conventions
Like all externally defined benchmark plugins for asv, this has a strict hierarchy.
- The package name begins with
asv_bench - Benchmarks are defined in a
benchmarksfolder under the package module - Each exported new benchmark type has the
export_as_benchmark = [NAMEBenchmark]attribute
For more conventions follow the documention of asv_runner.
License
MIT.
Metadata
Release files for asv_bench_memray 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| asv_bench_memray-0.1.2.tar.gz | 10.4 kB | Without provenance | Details for asv_bench_memray-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| asv_bench_memray-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for asv_bench_memray-0.1.2-py3-none-any.whl |
Total release size: 14.6 kB
Release files / asv_bench_memray-0.1.2.tar.gz
| Download URL | asv_bench_memray-0.1.2.tar.gz |
|---|---|
| Size | 10.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f00c552ee20c72c4885d70d7066da043855c62218ffbf2ac0f3f3c9bd99e8d2c
|
|
BLAKE2b-256 checksum How to use checksums |
9cda8b72a56c79131501f5466e33121d79fd9804059e7ad4164a4aa0aaac1e61
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
pdm/2.12.2 CPython/3.9.18
|
Release files / asv_bench_memray-0.1.2-py3-none-any.whl
| Download URL | asv_bench_memray-0.1.2-py3-none-any.whl |
|---|---|
| Size | 4.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5bde1fd68f75317f9f9d8129bc9360734cced91cf1ea7334559b21d305157f2f
|
|
BLAKE2b-256 checksum How to use checksums |
df4f16ae7ad03d54e8a2c5a9cd20bd1a13471713b74e4c30c5375e5df184e033
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
pdm/2.12.2 CPython/3.9.18
|
Security for asv_bench_memray 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.