From d48cda62936d21242aecbe91c1aa4f9dc3870302 Mon Sep 17 00:00:00 2001 From: "Steinar H. Gunderson" Date: Sun, 9 Jul 2017 00:54:51 +0200 Subject: [PATCH] Link to monitoring from the section on latency. --- hdmisdi.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/hdmisdi.rst b/hdmisdi.rst index 30fc5ee..a0a83b2 100644 --- a/hdmisdi.rst +++ b/hdmisdi.rst @@ -196,6 +196,12 @@ lowest and highest will be printed. Do note that the measurement is still done over a single *output* frame; it is *not* a measurement over the last 100 output frames, even though the statistics are only printed every 100th. +For more precise measurements, you can use Prometheus metrics to get percentiles +for all of these points, which will measure over all frames (over a one-minute +window). This yields more precise information than sampling every 100 frames, +but setting up Prometheus and a graphic tool is a bit more work, and usually not +worth it for simple measurement. For more information, see :doc:`monitoring`. + Another trick that can be useful in some situations is *looping* your signal, ie., connecting your output back into your input. This allows you to measure delays that don't happen within Nageru itself, like any external converters, -- 2.39.2