Skip to content

Revive benchmarks #2854

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Jun 10, 2025
Merged

Revive benchmarks #2854

merged 1 commit into from
Jun 10, 2025

Conversation

spectre-ns
Copy link
Contributor

@spectre-ns spectre-ns commented May 30, 2025 •
edited
Loading

Checklist

  • The title and commit message(s) are descriptive.
  • Small commits made to fix your PR have been squashed to avoid history pollution.
  • Tests have been added for new features or bug fixes.
  • API of new functions and classes are documented.

Description

@spectre-ns spectre-ns force-pushed the revive-benchmarks branch from d415ecc to 8e006f9 Compare May 30, 2025 23:45
@spectre-ns spectre-ns mentioned this pull request May 30, 2025
Open
@spectre-ns
Copy link
Contributor Author

@JohanMabille I added benchmarks across a couple compilers so we can regress on performance.

@spectre-ns spectre-ns changed the title [WIP] Revive benchmarks Revive benchmarks Jun 1, 2025
@JohanMabille JohanMabille merged commit 977aa1b into xtensor-stack:master Jun 10, 2025
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@JohanMabille JohanMabille JohanMabille approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@spectre-ns @JohanMabille