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

A windows machine won’t have ‘perf sched’. I don’t think Windows has similar lowlevel scheduling tracing - at least not that I remember. I suggest installing Linux on a separate partition and direct booting. Linux has a LOT of scheduling tracing/tuning options - some require a custom

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

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

I suggest you use the linux scheduler tracing facilities, e.g. perf shed to diagnose (see https://www.brendangregg.com/perf.html#SchedulerAnalysis ) But you may have to also do this outside the VM - to schedule trace the VM. In general,

[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