pandas-dev / pandas-dev/asv-runner
Commit 0efa9f0b98f70d82d6142943a8825f02037d21e4
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Subsequent benchmarks may have skipped some commits. The link above lists the commits that are between the two benchmark runs where the regression was identified.
- dtypes.SelectDtypes.time_select_dtype_string_include
-
dtype=<class 'float'> - 54.694% (22.384us)
-
dtype=<class 'int'> - 56.807% (22.972us)
-
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked commit range and the dtypes.SelectDtypes.time_select_dtype_string_include benchmark, including its float and int parameter cases. Run the benchmark through asv-runner and inspect the intervening commits to identify the regression. Done means the cause is identified and the benchmark no longer shows the reported slowdown.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100