-
-
Notifications
You must be signed in to change notification settings - Fork 214
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
Pipeline tests for jitter & dynamic latency #765
Comments
gavv
added a commit
to gavv/roc-toolkit
that referenced
this issue
Aug 6, 2024
…fix bugs - Use STS instead of system clock for timeouts. This allows to write fast pipeline tests not tied to real time. - Properly compare STS timestamps in LatencyEstimator. Old code was doing comparison without handling possible wrap in several places. - Adaptive latency fix: if new target is below minimum, but current target is above minimum, set target to the minimum instead of keeping target unmodified.
gavv
added a commit
to gavv/roc-toolkit
that referenced
this issue
Aug 6, 2024
- adaptive_latency_increase - adaptive_latency_decrease - adaptive_latency_upper_bound - adaptive_latency_lower_bound - metrics_jitter
gavv
added a commit
to gavv/roc-toolkit
that referenced
this issue
Aug 7, 2024
…fix bugs - Use STS instead of system clock for timeouts. This allows to write fast pipeline tests not tied to real time. - Properly compare STS timestamps in LatencyEstimator. Old code was doing comparison without handling possible wrap in several places. - Adaptive latency fix: if new target is below minimum, but current target is above minimum, set target to the minimum instead of keeping target unmodified.
gavv
added a commit
to gavv/roc-toolkit
that referenced
this issue
Aug 7, 2024
- adaptive_latency_increase - adaptive_latency_decrease - adaptive_latency_upper_bound - adaptive_latency_lower_bound - metrics_jitter
gavv
added a commit
to gavv/roc-toolkit
that referenced
this issue
Aug 7, 2024
…fix bugs - Use STS instead of system clock for timeouts. This allows to write fast pipeline tests not tied to real time. - Properly compare STS timestamps in LatencyEstimator. Old code was doing comparison without handling possible wrap in several places. - Adaptive latency fix: if new target is below minimum, but current target is above minimum, set target to the minimum instead of keeping target unmodified.
gavv
added a commit
to gavv/roc-toolkit
that referenced
this issue
Aug 7, 2024
- adaptive_latency_increase - adaptive_latency_decrease - adaptive_latency_upper_bound - adaptive_latency_lower_bound - metrics_jitter
gavv
added a commit
to gavv/roc-toolkit
that referenced
this issue
Aug 7, 2024
…fix bugs - Use STS instead of system clock for timeouts. This allows to write fast pipeline tests not tied to real time. - Properly compare STS timestamps in LatencyEstimator. Old code was doing comparison without handling possible wrap in several places. - Adaptive latency fix: if new target is below minimum, but current target is above minimum, set target to the minimum instead of keeping target unmodified.
gavv
added a commit
to gavv/roc-toolkit
that referenced
this issue
Aug 7, 2024
- adaptive_latency_increase - adaptive_latency_decrease - adaptive_latency_upper_bound - adaptive_latency_lower_bound - metrics_jitter
gavv
added a commit
to gavv/roc-toolkit
that referenced
this issue
Aug 7, 2024
…fix bugs - Use STS instead of system clock for timeouts. This allows to write fast pipeline tests not tied to real time. - Properly compare STS timestamps in LatencyEstimator. Old code was doing comparison without handling possible wrap in several places. - Adaptive latency fix: if new target is below minimum, but current target is above minimum, set target to the minimum instead of keeping target unmodified.
gavv
added a commit
to gavv/roc-toolkit
that referenced
this issue
Aug 7, 2024
- adaptive_latency_increase - adaptive_latency_decrease - adaptive_latency_upper_bound - adaptive_latency_lower_bound - metrics_jitter
gavv
added a commit
to gavv/roc-toolkit
that referenced
this issue
Aug 7, 2024
…fix bugs - Use STS instead of system clock for timeouts. This allows to write fast pipeline tests not tied to real time. - Properly compare STS timestamps in LatencyEstimator. Old code was doing comparison without handling possible wrap in several places. - Adaptive latency fix: if new target is below minimum, but current target is above minimum, set target to the minimum instead of keeping target unmodified.
gavv
added a commit
to gavv/roc-toolkit
that referenced
this issue
Aug 7, 2024
- adaptive_latency_increase - adaptive_latency_decrease - adaptive_latency_upper_bound - adaptive_latency_lower_bound - metrics_jitter
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
smoke test: automatic latency works (e.g.: enable latency tuning, run receiver for a while, check that niq latency is close to target; increase jitter, check that after a while niq latency is close to new target; decrease jitter, check; repeat a few times)
it would be also great to add same test, but with automatic latency disabled, and check that niq latency stays close to target no matter what is the jitter
smoke test: start latency works (set start latency different from target and see how niq latency starts with start_latency and goes to target)
smoke test: min/max latency works (bounding of target latency)
smoke test: jitter metric calculation
roc-toolkit/src/tests/roc_pipeline/test_receiver_source.cpp
Lines 3567 to 3570 in 987f5e3
The text was updated successfully, but these errors were encountered: