SPMI JIT metric diffs: use neutral grey colors instead of green/red for percentages#125155
SPMI JIT metric diffs: use neutral grey colors instead of green/red for percentages#125155
Conversation
…my JIT comment Co-authored-by: EgorBo <523221+EgorBo@users.noreply.github.com>
|
Tagging subscribers to this area: @JulieLeeMSFT, @jakobbotsch |
|
@copilot please make a dummy change that will have an impact on metrics, e.g. let's change the max assertions count to be 512 |
…mmy comment Co-authored-by: EgorBo <523221+EgorBo@users.noreply.github.com>
Done in 4a28673 — changed |
|
Hmm, it is quite hard to read without the green/red. Perhaps it is better to keep it, we just should be careful about how we interpret the numbers. (I am mainly worried that people will start optimizing for these numbers unmotivated...) |
yeah, doesn't look readable. let's keep it as is. |
JIT metric diffs used green/red coloring for negative/positive percentages, implying improvement/regression semantics that don't hold across all metrics — whether a metric going up or down is "good" varies by metric.
Changes
superpmi.py: Addneutralparameter (defaultFalse) toformat_pct(). WhenTrue, uses#888888(positive) and#555555(negative) instead of green/red. ASM diffs and throughput diffs are unaffected.write_metricdiff_markdown_summary: Add localfmt_pct/fmt_pct_ofwrappers that forward toformat_pct(..., neutral=True), replacing allformat_pct/compute_and_format_pctcalls in that function.assertionprop.cpp: Change max assertions count from 256 to 512 incountFuncto trigger metric diffs in CI and validate the color changes.Security
No security-relevant changes.
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.