Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Free telemetry from frame data #403

Open
planetchili opened this issue Jan 30, 2025 · 1 comment
Open

Free telemetry from frame data #403

planetchili opened this issue Jan 30, 2025 · 1 comment

Comments

@planetchili
Copy link
Collaborator

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.

@planetchili
Copy link
Collaborator Author

planetchili commented Jan 30, 2025

Requires #401 #284

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant