From 22d708aa5d33d25388b18ddafe86a5bf962dcdb8 Mon Sep 17 00:00:00 2001 From: Kimberly Meechan <24316371+K-Meech@users.noreply.github.com> Date: Fri, 16 Jan 2026 09:53:11 +0000 Subject: [PATCH 1/3] add pytest-benchmark to benchmarking section --- docs/pages/benchmarking-profiling.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/pages/benchmarking-profiling.md b/docs/pages/benchmarking-profiling.md index ea741bc1..65d60e32 100644 --- a/docs/pages/benchmarking-profiling.md +++ b/docs/pages/benchmarking-profiling.md @@ -5,9 +5,10 @@ layout: default ## Benchmarking -| Name | Short description | 🚦 | -| -------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :-----------------------------------------: | -| [asv](https://asv.readthedocs.io/en/stable/) | A tool for benchmarking Python packages over their lifetime. Allows you to write benchmarks and then run them against every commit in the repository, to identify where performance increased or decreased. Comparative benchmarks can also be run, which can be useful for [running them in CI using GitHub runners](https://labs.quansight.org/blog/2021/08/github-actions-benchmarks). | Best | +| Name | Short description | 🚦 | +| --------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------: | +| [asv](https://asv.readthedocs.io/en/stable/) | A tool for benchmarking Python packages over their lifetime. Allows you to write benchmarks and then run them against every commit in the repository, to identify where performance increased or decreased. Comparative benchmarks can also be run, which can be useful for [running them in CI using GitHub runners](https://labs.quansight.org/blog/2021/08/github-actions-benchmarks). | Best | +| [pytest-benchmark](https://pytest-benchmark.readthedocs.io/en/stable) | Provides a `benchmark` fixture with full `pytest` integration. A simple, light-weight alternative to `asv`, for cases that don't require tracking performance over many commits. | Good | ## Profiling From 24818243b0cfc12d1b24070f255d65d8a3b40e4e Mon Sep 17 00:00:00 2001 From: Kimberly Meechan <24316371+K-Meech@users.noreply.github.com> Date: Fri, 16 Jan 2026 16:10:58 +0000 Subject: [PATCH 2/3] update pytest-benchmark text --- docs/pages/benchmarking-profiling.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/benchmarking-profiling.md b/docs/pages/benchmarking-profiling.md index 65d60e32..2a950386 100644 --- a/docs/pages/benchmarking-profiling.md +++ b/docs/pages/benchmarking-profiling.md @@ -8,7 +8,7 @@ layout: default | Name | Short description | 🚦 | | --------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------: | | [asv](https://asv.readthedocs.io/en/stable/) | A tool for benchmarking Python packages over their lifetime. Allows you to write benchmarks and then run them against every commit in the repository, to identify where performance increased or decreased. Comparative benchmarks can also be run, which can be useful for [running them in CI using GitHub runners](https://labs.quansight.org/blog/2021/08/github-actions-benchmarks). | Best | -| [pytest-benchmark](https://pytest-benchmark.readthedocs.io/en/stable) | Provides a `benchmark` fixture with full `pytest` integration. A simple, light-weight alternative to `asv`, for cases that don't require tracking performance over many commits. | Good | +| [pytest-benchmark](https://pytest-benchmark.readthedocs.io/en/stable) | Provides a `benchmark` fixture with full `pytest` integration, and the ability to compare performance between multiple runs. A simple, light-weight alternative to `asv` that we've found to be useful. | Good | ## Profiling From b8bf82d23986523b0e56d880f93de77ff7a971b1 Mon Sep 17 00:00:00 2001 From: Kimberly Meechan <24316371+K-Meech@users.noreply.github.com> Date: Fri, 16 Jan 2026 16:14:12 +0000 Subject: [PATCH 3/3] remove backticks in pytest-benchmark description --- docs/pages/benchmarking-profiling.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/pages/benchmarking-profiling.md b/docs/pages/benchmarking-profiling.md index 2a950386..416d1edb 100644 --- a/docs/pages/benchmarking-profiling.md +++ b/docs/pages/benchmarking-profiling.md @@ -8,7 +8,7 @@ layout: default | Name | Short description | 🚦 | | --------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :------------------------------------------: | | [asv](https://asv.readthedocs.io/en/stable/) | A tool for benchmarking Python packages over their lifetime. Allows you to write benchmarks and then run them against every commit in the repository, to identify where performance increased or decreased. Comparative benchmarks can also be run, which can be useful for [running them in CI using GitHub runners](https://labs.quansight.org/blog/2021/08/github-actions-benchmarks). | Best | -| [pytest-benchmark](https://pytest-benchmark.readthedocs.io/en/stable) | Provides a `benchmark` fixture with full `pytest` integration, and the ability to compare performance between multiple runs. A simple, light-weight alternative to `asv` that we've found to be useful. | Good | +| [pytest-benchmark](https://pytest-benchmark.readthedocs.io/en/stable) | Provides a benchmark fixture with full pytest integration, and the ability to compare performance between multiple runs. A simple, light-weight alternative to asv that we've found to be useful. | Good | ## Profiling