cmd/trace: Mininum mutator utilization plot window durations range is not consistent across Include options #35330
Labels
compiler/runtime
Issues related to the Go compiler and/or runtime.
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I wrote a simple code to check built in golang tracing:
After running this program and getting
trace.out
file as an output I do$ go tool trace trace.out
, openhttp://127.0.0.1:32935/mmu
in the browser and look at the plots with and without STW checkbox set.What did you expect to see?
I expect that X-axis range (min and max Window duration for which MMU function is evaluated) is the same with STW set and not set.
What did you see instead?
I see that with STW checkbox set the window duration range is
[1ms, ~10s]
, and when checkbox is unset range is[1ns, 1ms]
.To conclude: if I get everything correctly, such behavior makes it harder to understand how GC affects the utilization. Should we make the window duration range consistent across any set of checked options? Or maybe we should make it possible for user to configure the range.
The text was updated successfully, but these errors were encountered: