Display target_tr for ndr/pdr results 26/24626/2
authorVratko Polak <vrpolak@cisco.com>
Wed, 29 Jan 2020 14:28:16 +0000 (15:28 +0100)
committerVratko Polak <vrpolak@cisco.com>
Wed, 29 Jan 2020 16:58:40 +0000 (17:58 +0100)
Small differences in Tx packet counts can cause
the previous way (which used transmit_rate,
computed from packets sent and nominal duration)
to report lower bounds as higher than upper bounds.

Also, reconf tests need the target (not actual) rate.

Change-Id: If5222dabd9762b8d9c2e22d875c12ad355bc6838
Signed-off-by: Vratko Polak <vrpolak@cisco.com>
resources/libraries/robot/performance/performance_utils.robot

index d6158a6..52ddc91 100644 (file)
 | | ... | doublings=${doublings} | traffic_directions=${traffic_directions}
 | | Check NDRPDR interval validity | ${result.pdr_interval}
 | | ... | ${packet_loss_ratio}
-| | Return From Keyword | ${result.pdr_interval.measured_low.transmit_rate}
+| | Return From Keyword | ${result.pdr_interval.measured_low.target_tr}
 
 | Find critical load using PLRsearch
 | | [Documentation]
 | |
 | | ${frame_size} = | Get Average Frame Size | ${frame_size}
 | | Display single bound | NDR_LOWER
-| | ... | ${result.ndr_interval.measured_low.transmit_rate} | ${frame_size}
+| | ... | ${result.ndr_interval.measured_low.target_tr} | ${frame_size}
 | | ... | ${result.ndr_interval.measured_low.latency}
 | | Display single bound | NDR_UPPER
-| | ... | ${result.ndr_interval.measured_high.transmit_rate} | ${frame_size}
+| | ... | ${result.ndr_interval.measured_high.target_tr} | ${frame_size}
 | | Display single bound | PDR_LOWER
-| | ... | ${result.pdr_interval.measured_low.transmit_rate} | ${frame_size}
+| | ... | ${result.pdr_interval.measured_low.target_tr} | ${frame_size}
 | | ... | ${result.pdr_interval.measured_low.latency}
 | | Display single bound | PDR_UPPER
-| | ... | ${result.pdr_interval.measured_high.transmit_rate} | ${frame_size}
+| | ... | ${result.pdr_interval.measured_high.target_tr} | ${frame_size}
 
 | Display result of soak search
 | | [Documentation]