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.

Sign up for GitHub

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

Jump to bottom

Dynamic latency improvements #712

Open
3 tasks
gavv opened this issue Apr 2, 2024 · 0 comments
Open
3 tasks

Dynamic latency improvements #712

gavv opened this issue Apr 2, 2024 · 0 comments
Assignees
@gavv
Labels
enhancement

Comments

@gavv
Copy link
Member

gavv commented Apr 2, 2024 •
edited
Loading

Follow-up for #688, tasks for future releases:

  • Don't start session from fixed latency. Instead, start from min latency, wait until accumulated amount becomes larger than jitter or max latency, and then start session.
  • Don't take into account short jitter spikes. Maybe use running percentile instead of running maximum.
  • Use running maximum for estimated FEC block duration.
@gavv gavv added this to Roc Toolkit Jul 6, 2024
@gavv gavv moved this to Frontlog in Roc Toolkit Jul 6, 2024
This was referenced Jul 12, 2024
Closed
Closed
@gavv gavv mentioned this issue Jul 30, 2024
Open
gavv added a commit to gavv/roc-toolkit that referenced this issue Aug 11, 2024
@gavv
roc-streaminggh-712: Improve peak jitter calculations
28e74a0 
- Extract JitterMeter class.
- Remove `min_jitter` metric (it is almost always zero or very
  close to it).
- Replace `max_jitter` with `peak_jitter`, which is similar to
  maximum, but tries to exclude harmless spikes to reduce latency.

See comments in JitterMeter for details on the algorithm.
@gavv gavv mentioned this issue Aug 11, 2024
Merged
gavv added a commit to gavv/roc-toolkit that referenced this issue Aug 13, 2024
@gavv
roc-streaminggh-712: Improve peak jitter calculations
f1c5b24 
- Extract JitterMeter class.
- Remove `min_jitter` metric (it is almost always zero or very
  close to it).
- Replace `max_jitter` with `peak_jitter`, which is similar to
  maximum, but tries to exclude harmless spikes to reduce latency.

See comments in JitterMeter for details on the algorithm.
gavv added a commit to gavv/roc-toolkit that referenced this issue Aug 13, 2024
@gavv
roc-streaminggh-712: Improve peak jitter calculations
2c84c4f 
- Extract JitterMeter class.
- Remove `min_jitter` metric (it is almost always zero or very
  close to it).
- Replace `max_jitter` with `peak_jitter`, which is similar to
  maximum, but tries to exclude harmless spikes to reduce latency.

See comments in JitterMeter for details on the algorithm.
gavv added a commit that referenced this issue Aug 13, 2024
@gavv
gh-712: Improve peak jitter calculations
21f8dfe 
- Extract JitterMeter class.
- Remove `min_jitter` metric (it is almost always zero or very
  close to it).
- Replace `max_jitter` with `peak_jitter`, which is similar to
  maximum, but tries to exclude harmless spikes to reduce latency.

See comments in JitterMeter for details on the algorithm.
@gavv gavv self-assigned this Nov 27, 2024
@gavv gavv moved this from Frontlog to In work in Roc Toolkit Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@gavv gavv

Labels
enhancement
Projects
Roc Toolkit
Status: In work
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gavv