Re: [go-nuts] cmd/trace: Indirect reporting of OS Latency?

Robert, thanks for your reply - especially the link to *perf sched*! I plan to run the go program on Windows physical machine. I'll post my results once done. -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and

[go-nuts] cmd/trace: Indirect reporting of OS Latency?

*TLDR* I’d be grateful if someone could either confirm or dismiss the effect of OS, go runtime, and/or Hypervisor latency on the output of a goroutine trace. The trace report displays empty gaps of 3-14ms where expected periodic goroutines should execute, as there’s a goroutine triggered by

Re: [go-nuts] Trace explicit goroutine function names replaced by synthetic ones 1.18beta1

Ian: Appreciate your guidance. Created issue #50622 <https://github.com/golang/go/issues/50622>. Rich On Friday, January 14, 2022 at 1:12:38 PM UTC-5 Ian Lance Taylor wrote: > On Fri, Jan 14, 2022 at 10:03 AM Rich Moyse wrote: > > > > When viewing a trace

[go-nuts] Trace explicit goroutine function names replaced by synthetic ones 1.18beta1

When viewing a trace produced by 1.18beta1, the goroutine function names reflect synthetically generated ones typically assigned to anonymous/closure functions. For example, a function explicitly named: "*msgSend*" in the "main" package appears on the trace "/goroutines" page as:

[go-nuts] generics go2go Type List in Interface - Struct Type

Attempting to use a Type List in an Interface to restrict the types allowed to instantiate a generic function (example in go2go