You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I hope this isn't spam but I have a few questions after reading the blog post and the README, and playing with this a little more:
You write "[user START/STOP event] periods are completely independent of threads". Am I right that this means we can't just e.g. wrap a handler function HttpRequest -> IO JSON in traceEventIO "START/STOP mainHandlerFunc" and expect it to give sensible results (since STARTs and STOPs will be interleaved across threads, and ghc-events-analyze will pair a START from one thread with a STOP from a different one)?
If so is this a usecase for "Event subscripts", where I could do above but hash the threadID and use that as a subscript, allowing us to correlate stops and starts?
How should I understand how the tool behaves when there is nesting (START foo >> START bar >> STOP bar >> STOP foo)? It looks like that is supported but it's the users job to make note of when that's happening and what part of the time of an event should be attributed to a child event. I'm just interested in being able to use the same instrumentation to be able to get a more traditional profiling report as well, and I'm curious what you think about that (see also Chrome Trace Event support? #29)
The text was updated successfully, but these errors were encountered:
interleaved "START ... STOP" spans are collapsed (as expected?) in the "User Events" timeline, where I guess they have the meaning "an event is running on some thread"
using "subscripts" causes them to be shown separated in "User Events" timeline
nested "START ... STOP" spans that use subscripts generate separate User Event spans without trouble also; but there's no information associating these spans with each other or a particular entry in the "Thread Events" timeline
I hope this isn't spam but I have a few questions after reading the blog post and the README, and playing with this a little more:
HttpRequest -> IO JSON
intraceEventIO "START/STOP mainHandlerFunc"
and expect it to give sensible results (since STARTs and STOPs will be interleaved across threads, and ghc-events-analyze will pair a START from one thread with a STOP from a different one)?START foo >> START bar >> STOP bar >> STOP foo
)? It looks like that is supported but it's the users job to make note of when that's happening and what part of the time of an event should be attributed to a child event. I'm just interested in being able to use the same instrumentation to be able to get a more traditional profiling report as well, and I'm curious what you think about that (see also Chrome Trace Event support? #29)The text was updated successfully, but these errors were encountered: