perf: Optimize memory allocations and string operations #37
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
- Use strings.Builder instead of += concatenation in benchmark test - Pre-allocate slices with known capacity in ParsePathFile, extractJobOrderFromNode, and DiscoverWorkflows - Use strings.EqualFold for case-insensitive comparison instead of strings.ToLower to avoid unnecessary string allocations These changes reduce memory allocations and improve performance by: - Avoiding O(n²) string concatenation in loops - Reducing slice reallocations during append operations - Eliminating temporary string allocations for case comparison
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.
extractJobOrderFromNode, and DiscoverWorkflows
strings.ToLower to avoid unnecessary string allocations
These changes reduce memory allocations and improve performance by: