[Fuego] [PATCH 5/5] cyclictest:add min_latency graph

Tim.Bird at sony.com Tim.Bird at sony.com
Wed Dec 12 00:56:17 UTC 2018

Zhong Lu,

I applied all 5 patches in this series, but I do have a question about this one
and patch 2/5.  Both of these add min_latency values to the charts for their
respective tests.

Can you please let me know why this is something you would like to see charted?
I'm not sure it provides any value to the end user (tester), and it will tend to clutter
up the graph.   I don't know if the min_latency is ever very useful, unless it is very high
which would show something really, really wrong with the realtime scheduling on
the board.

I have already applied the patches (along with similar ones from Liu Gang).  So
it's not critical.  But if you have some more information about your use of this
measurement I would appreciate hearing about it.

 -- Tim

> -----Original Message-----
> From: Zhong Lu
> details:details:Test case 'min_latency' is defined and value is checked, but
> there is no graph.
> Add graph of 'min_latency'.
> Signed-off-by: Zhong Lu <zhongl.fnst at cn.fujitsu.com>
> ---
>  engine/tests/Benchmark.cyclictest/chart_config.json | 1 +
>  1 file changed, 1 insertion(+)
> diff --git a/engine/tests/Benchmark.cyclictest/chart_config.json
> b/engine/tests/Benchmark.cyclictest/chart_config.json
> index cdaf6a2..aa73167 100644
> --- a/engine/tests/Benchmark.cyclictest/chart_config.json
> +++ b/engine/tests/Benchmark.cyclictest/chart_config.json
> @@ -1,5 +1,6 @@
>  {
>  	"chart_type": "measure_plot",
>  	"measures": ["default.latencies.max_latency",
> +        "default.latencies.min_latency",
>          "default.latencies.avg_latency"]
>  }
> --
> 2.7.4

More information about the Fuego mailing list