create environments with older package versions #173
Merged
Conversation
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
Contributor
I think its a handy utility to have, e.g., for debugging performance issues, so including in the code base is fine with me |
Contributor
Author
|
@rly - as part of your upcoming benchmarks runs you could also include runs using the environments created by this script. Otherwise I can take some time on the lbl-mac to generate those results after you are done with your initial runs. |
rly
reviewed
Nov 8, 2025
rly
approved these changes
Nov 14, 2025
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.
As part of #89, we discussed looking at how performance for specific metrics changes over time.
This utility script will create environment files to use for testing older versions of our key streaming packages of interest. I'm not sure if it's worth including in the codebase or adding in the scripts folder since future monitoring of changes across time can just pull different package versions from the benchmarks results database.
To generate the results for the older version, create and activate the conda environment with a specified date limit.