Closed olichtne closed 8 months ago
I have just one question about the output.
I see that there is:
host host1 cpu 'cpu' utilization: 130.86 +-16.58 time units per second
New utilization average is 0.00% higher from the baseline. Allowed difference: 1.0%
and
Generator measured throughput: 1221659418.30 +-59245322.92(4.85%) bits per second.
Generator process CPU data: 44.93 +-0.03 cpu_percent per second.
Receiver measured throughput: 1213241304.82 +-58536978.08(4.82%) bits per second.
Receiver process CPU data: 24.82 +-0.23 cpu_percent per second.
New generator_results average is 0.00% higher from the baseline. Allowed difference: 1.0%
New generator_cpu_stats average is 0.00% higher from the baseline. Allowed difference: 1.0%
New receiver_results average is 0.00% higher from the baseline. Allowed difference: 1.0%
New receiver_cpu_stats average is 0.00% higher from the baseline. Allowed difference: 1.0%
I'm wondering if we could change the output so that the individual metric names are same in both metric measurement description and metric evaluation description, that is e.g:
Generator measured throughput (generator_results): 1221659418.30 +-59245322.92(4.85%) bits per second.
Generator process CPU data (generator_cpu_stats): 44.93 +-0.03 cpu_percent per second.
Receiver measured throughput (receiver_results): 1213241304.82 +-58536978.08(4.82%) bits per second.
Receiver process CPU data (receiver_cpu_stats): 24.82 +-0.23 cpu_percent per second.
New generator_results average is 0.00% higher from the baseline. Allowed difference: 1.0%
New generator_cpu_stats average is 0.00% higher from the baseline. Allowed difference: 1.0%
New receiver_results average is 0.00% higher from the baseline. Allowed difference: 1.0%
New receiver_cpu_stats average is 0.00% higher from the baseline. Allowed difference: 1.0%
or ideally (I'm aware that this would require metric name to human readable name translation):
Generator measured throughput (generator_results): 1221659418.30 +-59245322.92(4.85%) bits per second.
...
Generator measured throughput average is 0.00% higher from the baseline. Allowed difference: 1.0%
It is probably out of scope of this MR and could be done separately.
Generator measured throughput (generator_results): 1221659418.30 +-59245322.92(4.85%) bits per second.
this should be simple so i'll do at least that in this PR
added one more commit that makes the OvSDPDKPvPRecipe and VhostNetPvPRecipe use hostids consistent with the rest of the enrt recipes
Tested the OvSDPDKRecipe in J:8895512
, and we don't currently run the VhostNetPvPRecipe so i didn't test that...
Description
This implements some much needed refactoring of MeasurementResults and the BaselineEvaluator and as such brings some reduction and unification of the relevant code.
Tests
Tested locally with some custom changes to use the "current result -> baseline result" and "threshold = 1" code adjustments with the following recipe:
After running this this is what the evaluation result descriptions look like:
Additionally if you remove the "cpu evaluation filters" this is what we get:
so an interleaving of "result.description" and "comparison.description"...