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
This series adds the performance format target for TRACE2 tracing.
The first two patches are small fixes for bugs I noticed as I was
testing the
performance format target. The first moves the `FormatTargetTypes` enum
from the specific `Trace2StreamWriter` class to the shared
`Trace2Writer`
class. The second ensures the normal format event names are written in
snake
case (rather than lowercase).
The third patch adds the ability to get the "depth" of the process.
Because Sids
and depth are process-related concepts, it removes the SidManager class
and
moved depth/sid-related properties and methods into the ProcessManager
class.
The fourth patch adds the performance format target. It includes a few
notable
components:
1. A new GetMessage method to ensure message strings written to normal
and
performance targets are not duplicated.
2. A new PerformanceFormatComponent class to track sizing of optional
properties of performance format messages.
3. A BuildSpan method that Trace2Message children use to create
correctly-sized "spans" for optional properties of performance format
messages. A span is a piece of the message beginning with a pipe (|) and
ending just before the next pipe or the end of the message.
4. A BuildTimeSpan method that adjusts spans for long/short times. In
future, when we have events that include performance format string span
components, we will need to add an additional method to handle them.
0 commit comments