Thanks Chris
On Monday, October 7, 2019 at 10:40:22 AM UTC-7, Chris Hines wrote:
>
> I am pretty sure that a "proc" in the trace visualization output is the
> same as a "P" in the parlance of the Go runtime scheduler. In the scheduler
> an OS thread is an "M" and even when using LockOSThread the
I am pretty sure that a "proc" in the trace visualization output is the
same as a "P" in the parlance of the Go runtime scheduler. In the scheduler
an OS thread is an "M" and even when using LockOSThread the locked
goroutine and thread need to be paired up with one of the scheduler's Ps in
orde
