I do not see the actual results of the DTS perf test in the links you
posted, only percentage of degradation or improvement, unless I miss
something.
This was done on purpose as requested by the Members participating in the effort. This CI is meant for the DPDK maintainers to make sure that a patch does not introduce significant performance regressions on various hardware platforms, or to show how a patch may improve the performance of DPDK on these platforms (such as driver updates or something in the core of DPDK itself). It is not to compare the performance between different devices.
I believe it can be helpful if the baseline of the actual results will also be shownÂ
to enable comparing to other vendors besides Intel and Mellanox.
There is not a single baseline for all devices. The baselines are generated per device. Knowing the baseline would allow creating an absolute result, which we are trying to avoid.
Do you plan to add such URL in the report sent to patchwork?
Instead of filtering based on the label, you could filter based on
the paths of modified files.
Note that such filter depends on the test you run,
because you could also test the doc syntax in the CI.
Okay, so if a series only modified the doc folder, then don't include it for performance tests. Later on, we can introduce syntax checking for documentation when we introduce more unit testing / functional testing.
https://bugs.dpdk.org/show_bug.cgi?id=181