test/qos: allow more variance due to iSCSI overhead
Running iSCSI in loopback runs into some cases where a core is considerably impacted by the initiator TCP traffic, even though the scheduler is trying to schedule it on different cores. Gang is working through modifying the QoS tests to just use bdevperf instead of iSCSI, but until that is ready, let's allow more variance to reduce the fairly significant rate of test failures we're seeing due to this test. Signed-off-by: Jim Harris <james.r.harris@intel.com> Change-Id: I99fe13621f5ca2f8e6402fc17fb859df815fe05e Reviewed-on: https://review.gerrithub.io/c/444458 Reviewed-by: Ben Walker <benjamin.walker@intel.com> Reviewed-by: Shuhei Matsumoto <shuhei.matsumoto.xt@hitachi.com> Reviewed-by: Changpeng Liu <changpeng.liu@intel.com> Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
This commit is contained in:
parent
c217d7287d
commit
5ab609b3bb
@ -32,7 +32,7 @@ function check_qos_works_well() {
|
||||
|
||||
if [ $enable_limit = true ]; then
|
||||
#qos realization is related with bytes transfered.It currently have like 5% variation.
|
||||
retval=$(echo "$qos_limit*0.95 < $read_result && $read_result < $qos_limit*1.05" | bc)
|
||||
retval=$(echo "$qos_limit*0.85 < $read_result && $read_result < $qos_limit*1.05" | bc)
|
||||
if [ $retval -eq 0 ]; then
|
||||
echo "Failed to limit the io read rate of malloc bdev by qos"
|
||||
exit 1
|
||||
|
Loading…
Reference in New Issue
Block a user