Profile zstash check#450
Draft
forsyth2 wants to merge 21 commits into
Draft
Conversation
Collaborator
Author
|
The first 17 commits are from #427. They will be removed from this PR once that PR is merged and I rebase this branch. |
Collaborator
Author
|
Prototype of Fig 3 (
Remaining action items:
|
Collaborator
Author
|
Prototype of Fig 3b (the comparison) using yesterday's main-branch/Unified baseline and a "current" of the #447's code (the
|
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
Objectives:
zstash check.Issue resolution:
zstash check#446 (one component. The other component is actually improving the efficiency ofzstash check; that is covered by Speed upzstash checkmultiprocessing scheduling and queue handling #447).Select one: This pull request is...
Small Change