Thanks Ian. I'm using schedtrace and scheddetail to help understand the scheduling flow, the minimum monitoring window seems to be 1ms only, possible to get more detailed info? Furthermore, sched* outputs extensive logs but what I expect, at present, might be something like when a goroutine is parked due to what reason, etc., can I get it with the existing diagnostics?
On Thursday, March 5, 2020 at 11:24:23 AM UTC+8, Ian Lance Taylor wrote: > > On Wed, Mar 4, 2020 at 6:44 PM Xiangdong JI <xiang...@arm.com > <javascript:>> wrote: > > > > Given the attached screenshot of pprof output, I wonder how to figure > out the callers of 'runtime.mcall' and their cost? Thanks. > > You can't, but it doesn't matter. The mcall function is used when a > thread changes from executing one goroutine to a different goroutine. > Knowing the code that triggers the call into mcall won't tell you > anything. It's just where that goroutine happened to be preempted. > > Ian > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/71ecd07a-0b42-4eba-9b22-5c7cc9821243%40googlegroups.com.
