astropy / astropy/astropy-benchmarks

How we do benchmarking

Open
#120 11 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
9
Forks
35
Avg merge
2d 3h
Merged PRs (30d)
1

Description

Is there a reason, beyond historical, that we use `ASV` over `pytest-benchmark` ?
Looking at the two tools, `pytest-benchmark` has 1.5x more stars and 8x greater usage (as measured by GH dependencies). Also `pytest-benchmark` integrates into our existing pytest framework so that this repo might pull tests directly from `astropy`'s test suite, using a `pytest` Mark (e.g. `pytest.mark.benchmark_only`).

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the existing ASV setup and the repository's use of pytest, then compare how pytest-benchmark could integrate with the astropy test suite through a benchmark-only mark. Done would require a maintainer decision on whether to retain ASV or pursue a migration, with the chosen rationale and scope documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
performance, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.