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
Having the telemetry data tied to frames in the IPC shared memory has several drawbacks:
Redundant telemetry usage when frame rate exceeds telemetry sample rate
Redundancy when tracking multiple processes
Redundancy multiplied by number of devices in multi-device scenarios
Inability to measure telemetry when frame rate is low / non-existent
Extra work aligning telemetry data that may not be consumed
Storing the telemetry samples in its own structure at a different rate than frame rate solves this. This means when alignment is done (during frame data event capture), it will be done on the middleware side on demand.
The text was updated successfully, but these errors were encountered:
Having the telemetry data tied to frames in the IPC shared memory has several drawbacks:
Storing the telemetry samples in its own structure at a different rate than frame rate solves this. This means when alignment is done (during frame data event capture), it will be done on the middleware side on demand.
The text was updated successfully, but these errors were encountered: