Thanks Marco. Indeed these 1-pixel-wide events have titles "syscall", "proc stoc", this in not really comparable with the first line.
On Thursday, January 12, 2017 at 2:35:21 PM UTC+1, Marko Kevac wrote: > > Library which is used to draw this charts have few event types internally. > Some event types have begin and an end (let's call them "events with > duration"), some are instant. > An instant event can happen asynchronously (at the same time) with an > event with duration. In that case, chart library puts instant events in a > second row (line). > > On Wednesday, January 11, 2017 at 3:08:07 PM UTC+3, Val wrote: >> >> Hello >> trying to analyze and optimize the work load of my goroutines, I'm using >> the Trace <https://golang.org/cmd/trace/> web viewer and visualize the >> work of each of my processors : >> >> >> >> <https://lh3.googleusercontent.com/-WVJau-oABcU/WHYdFVtXZ_I/AAAAAAAAAdc/7qfogCmWy2IqrNSFuriSc57QXNUZ0doIACLcB/s1600/trace_procs.png> >> >> <https://lh3.googleusercontent.com/-KHPKC5yNGLQ/WHYftcQIw7I/AAAAAAAAAd4/zbkeRPm8i_4DM3JCju38PBQEGN5-KGzygCLcB/s1600/trace_procs_2nd_line.png> >> >> >> Really useful, I love it! >> >> *My question is* : what is the second line (which is sparser) for each >> proc? >> does it mean that each of my physical cores has 2 logical cores? Is it >> related to hyperthreading? >> Does it mean there "might be" some way of programming the tasks to better >> fill the second line, thus increasing overall speed? >> Thank you for insight! >> Val >> > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
