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
Seems like using either t0 or t4 would be the most useful. This way all of the phase timings could be easily translated to absolute times by an external tool.
A timestamp for gctrace=1's output would be very useful for external tooling wishing to visualize or aggregate gc logs.
Relevant log line: https://github.com/golang/go/blob/master/src/runtime/mgc.go#L1668-L1676
Seems like using either t0 or t4 would be the most useful. This way all of the phase timings could be easily translated to absolute times by an external tool.
Original post: https://groups.google.com/forum/#!topic/golang-nuts/CG4BrJ0ZD6Q
The text was updated successfully, but these errors were encountered: