perf(layer-loading): establish baseline and instrumentation [1/5] - #185
Open
Anthony Cintron (prbatero) wants to merge 1 commit into
Open
perf(layer-loading): establish baseline and instrumentation [1/5]#185Anthony Cintron (prbatero) wants to merge 1 commit into
Anthony Cintron (prbatero) wants to merge 1 commit into
Conversation
Measure the project-details N+1 path before changing runtime behavior. Add opt-in logical operation timing, deterministic synthetic fixtures, HTTP and browser benchmark tools, a reproducible Compose overlay, and the feature specification.
11 tasks
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
Part 1 of 5 in the project layer-loading performance stack. Establish a reproducible baseline and opt-in observability before changing runtime behavior.
Changes
HASTE_PERF.Testing
Stack
main.prbatero/feat/perf-data-layer-core.Review Notes
This PR intentionally adds measurement and documentation before the optimization. Runtime behavior is unchanged unless
HASTE_PERF=true.