Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable performance tracking via continuous benchmarking. #13460

Merged
merged 14 commits into from
Jan 9, 2024
Merged

Conversation

jezdez
Copy link
Member

@jezdez jezdez commented Dec 22, 2023

Description

This sets up codespeed following their docs: https://docs.codspeed.io/ci/github-actions

I've selected a number of basic tests to run for now, we can tweak that list in the future.

Checklist - did you ...

  • Add a file to the news directory (using the template) for the next release's release notes?
  • Add / update necessary tests?
  • [ ] Add / update outdated documentation?

@jezdez jezdez changed the title Enable codespeed performance tracking. Enable performance tracking via continuous benchmarking. Dec 22, 2023
@conda-bot conda-bot added the cla-signed [bot] added once the contributor has signed the CLA label Dec 22, 2023
Copy link

codspeed-hq bot commented Jan 3, 2024

CodSpeed Performance Report

Congrats! CodSpeed is installed 🎉

🆕 0 new benchmarks were detected.

You will start to see performance impacts in the reports once the benchmarks are run from your default branch.

Detected benchmarks

@jezdez jezdez marked this pull request as ready for review January 3, 2024 00:17
@jezdez jezdez requested a review from a team as a code owner January 3, 2024 00:17
.github/workflows/tests.yml Outdated Show resolved Hide resolved
travishathaway
travishathaway previously approved these changes Jan 8, 2024
@@ -210,11 +214,11 @@ def test_env_remove(conda_cli: CondaCLIFixture, tmp_env: TmpEnvFixture):
assert not code


@pytest.mark.benchmark
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the future I'd rather see a tests/benchmarks/ directory with benchmark-focused tests so we don't mix IO too much, since codspeed since to be focusing on CPU bound tasks.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, that makes sense, I even started with it at first and then noticed that I was duplicating a lot of efforts. I started from the tests in conda-benchmarks, but thought to first get some experience with codspeed.

jaimergp
jaimergp previously approved these changes Jan 8, 2024
dev/linux/benchmarks.sh Outdated Show resolved Hide resolved
@jezdez jezdez dismissed stale reviews from jaimergp and travishathaway via 9065ab4 January 8, 2024 21:04
Co-authored-by: Ken Odegard <kodegard@anaconda.com>
@jezdez jezdez requested a review from kenodegard January 8, 2024 21:05
@jezdez jezdez enabled auto-merge (squash) January 8, 2024 21:05
@jezdez jezdez merged commit ec4eadb into main Jan 9, 2024
75 checks passed
@jezdez jezdez deleted the benchmarks branch January 9, 2024 00:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla-signed [bot] added once the contributor has signed the CLA
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

None yet

5 participants