You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Round 2 of AGENTS.md cleanups (follow-up to #8554), continuing the agents.md best practices "table of contents, not encyclopedia" principle.
Reason for change
Five targeted improvements: collapse provably redundant sections, drop stale references, fix broken formatting. Every line in AGENTS.md is loaded into agent context on every task, so redundant content has a real cost.
Implementation details
#
Change
1
NuGet Package Architecture: collapse 3 sub-sections that all described the same package/DLL distinction into 2 paragraphs
2
Drop the stale **Reference:** See PR 7467... citation in Logging
3
Drop the generic **Filters:** --filter "Category=Smoke", --framework net6.0 line in Testing (derivable from dotnet test --help)
4
Trim Commit & PR Guidelines: drop universal git/PR advice (imperative mood, link issues, etc.); keep only the repo-specific [Area] prefix convention and the "keep concise" rule (the latter is specifically AI-relevant — agents tend to over-explain)
5
Reformat the multi-line supported-configurations.yaml Configuration bullet into a single line (was rendering oddly)
Comparing candidate commit 41344d6 in PR branch nacho/AgentsMdImprove2 with baseline commit d43a6e5 in branch master.
Some scenarios are present only in baseline or only in candidate runs. If you didn't create or remove some scenarios in your branch, this maybe a sign of crashed benchmarks 💥💥💥
Check Gitlab CI job log to find if any benchmark has crashed.
Found 3 performance improvements and 5 performance regressions! Performance is the same for 45 metrics, 19 unstable metrics, 93 known flaky benchmarks, 33 flaky benchmarks without significant changes.
Explanation
This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:
🟩 = significantly better candidate vs. baseline
🟥 = significantly worse candidate vs. baseline
We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.
If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.
Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.
More details about the CI and significant changes
You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.
CIs of the difference of means are often centered around 0%, because often changes are not that big:
---------------------------------(------|---^--------)-------------------------------->
-0.6% 0% 0.3% +1.2%
| | |
lower bound of the CI --' | |
sample mean (center of the CI) -------------' |
upper bound of the CI ----------------------'
As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).
For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:
----------------------------------------|---------|---(---------^---------)---------->
0% 1% 1.3% 2.2% 3.1%
| | | |
significant impact threshold --------------' | | |
lower bound of CI --------------' | |
sample mean (center of the CI) --------------------------' |
upper bound of CI ----------------------------------'
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
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 of changes
Round 2 of
AGENTS.mdcleanups (follow-up to #8554), continuing the agents.md best practices "table of contents, not encyclopedia" principle.Reason for change
Five targeted improvements: collapse provably redundant sections, drop stale references, fix broken formatting. Every line in
AGENTS.mdis loaded into agent context on every task, so redundant content has a real cost.Implementation details
**Reference:** See PR 7467...citation in Logging**Filters:** --filter "Category=Smoke", --framework net6.0line in Testing (derivable fromdotnet test --help)[Area]prefix convention and the "keep concise" rule (the latter is specifically AI-relevant — agents tend to over-explain)supported-configurations.yamlConfiguration bullet into a single line (was rendering oddly)Net: +5 / -33 lines.
AGENTS.mdis now 305 lines.Test coverage
N/A — documentation-only.