Currently the monitoring/graphing of metrics and frame event data (typically via the overlay) has a hard limit of 1 second of latency. This is the because ETW batches events together, invoking the callback in bursts at an interval of 1 sec.
Understandably, the user experience suffers because of this, and it also complicates some aspects of metric processing.
It appears to be possible to manually flush the trace buffers with by using a FLUSH control command. Therefore, it should be possible to achieve latencies order(s) of magnitude lower than we currently have.
Currently the monitoring/graphing of metrics and frame event data (typically via the overlay) has a hard limit of 1 second of latency. This is the because ETW batches events together, invoking the callback in bursts at an interval of 1 sec.
Understandably, the user experience suffers because of this, and it also complicates some aspects of metric processing.
It appears to be possible to manually flush the trace buffers with by using a FLUSH control command. Therefore, it should be possible to achieve latencies order(s) of magnitude lower than we currently have.