Open
Conversation
Pull Request Test Coverage Report for Build 3921274111
💛 - Coveralls |
PatrickCronin
force-pushed
the
pcronin/performance-feature-branch
branch
4 times, most recently
from
04aba48 to
101f1df
Compare
PatrickCronin
force-pushed
the
pcronin/performance-feature-branch
branch
2 times, most recently
from
919d6ed to
1bb8216
Compare
PatrickCronin
force-pushed
the
pcronin/performance-feature-branch
branch
from
ac52555 to
8f16126
Compare
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
2 participants
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.
Over the course of making routesum faster, we've tried a number of things, and added a few features that are great for monitoring both performance and memory usage. Up to this point we've been merging these straight into main. In retrospect, some of these changes are useful only temporarily, and so don't really belong in main. This PR (well, this branch really) will store the useful changes that will support the performance and memory monitoring, and can be the branch upon which all current performance tweaks can be based on, before selecting the winning branch, rebasing it on main, and merging that.