pandas-dev / pandas-dev/asv-runner

Commit 0efa9f0b98f70d82d6142943a8825f02037d21e4

Open
#154 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

pending fix
Dominant language
Python
Stars
3
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Commit Range

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.