Merged
Conversation
1819371 to
242ab63
Compare
Contributor
Author
Congrats! CodSpeed is installed 🎉
You will start to see performance impacts in the reports once the benchmarks are run from your default branch.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
pytest-codspeed(already a dev dependency) covering the core modules:Stream,Result, utility functions (compose,all_of,any_of,identity,invert), andnew_type..github/workflows/codspeed.yml) that runs benchmarks on every push tomain, on pull requests, and on manual dispatch. It uses OIDC authentication and simulation mode.Benchmark coverage
map,filter, chained map+filter,fold,partitionat small and medium sizesOk/Errcreation,mapchaining,and_thenchaining,Errshort-circuit,unwrap, stream-of-results pipelinecompose,all_of,any_of,identity,invertmap, creation with convertersNote on runners
This repository belongs to a personal GitHub account. The workflow uses
ubuntu-latestrunners instead ofcodspeed-macrorunners, which are only available for organization repositories. This means performance variance will be higher than with dedicated macro runners. See walltime docs for more details. Since this workflow uses simulation mode (not walltime), this is less of a concern -- simulation mode provides consistent measurements regardless of runner hardware.Next steps
mainestablish baseline measurements.par_collectandasync_collectif parallel/async performance tracking is desired.