Add Azurite-backed memory stress benchmarks to OC - #1496
Closed
ricardo-devis-agullo wants to merge 4 commits into
Closed
Add Azurite-backed memory stress benchmarks to OC#1496ricardo-devis-agullo wants to merge 4 commits into
ricardo-devis-agullo wants to merge 4 commits into
Conversation
ricardo-devis-agullo
force-pushed
the
opencode/eager-canyon
branch
from
June 14, 2026 12:54
d7e7b28 to
4b7124c
Compare
Collaborator
Author
|
Closing — large Azurite benchmark harness is not a current priority. Can revisit as a fresh PR if we need memory stress benchmarks later. |
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
1 participant
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.
Introduces Azurite-backed benchmark scenarios that simulate a large component registry, generate heavy component metadata, and track peak heap/RSS usage to validate memory consumption improvements.