Network slowness with QoS Session

Review Request #312 — Created July 3, 2024 and updated

pradeep
APV10
10_4_0_112_gail
902
kdutta, prajesh, roland, tanya

At customer environment we see users experiencing slowness at random times at random PPS. Changes made to improve the mbuf processing. Also too many debug logs were adding to the slowness.

Tested with high PPS 70K pps IN/OUT (which more then double the PPS seen at customer place[peak time].)

below are the configs used.

log level "info"
log off

qos interface "port5" OUT 3Gb
qos enable "port5" OUT
qos interface "port5" IN 3Gb
qos enable "port5" IN
qos queue root "q_default_port5_out" "port5" OUT 3Gb 1 UNBORROW DEFAULT
qos queue root "q_default_port5_in" "port5" IN 3Gb 1 UNBORROW DEFAULT
qos sessionon
qos sespacketcnt 50
qos sessionqdelstepcount 1
qos qlenwait 1027
qos qosclasscnt 48
qos qosclspos 8

Description From Last Updated

do you need this log?

prajeshprajesh

remove space

kduttakdutta

t = 2 is already there before the log.

prajeshprajesh

same

kduttakdutta

This sounds a kludge to me. We should debug why and when is this happening.

prajeshprajesh
prajesh
  1. 
      
  2. t = 2 is already there before the log.

    1. thats the 'else' part. There is a different calculation for 'if' clause.

  3. 
      
kdutta
pradeep
Review request changed
prajesh
  1. 
      
  2. This sounds a kludge to me. We should debug why and when is this happening.

    1. effectively this clause will always be false.
      We have reset the qlen to original 1024 packets.(from 2048 packets). So enqueue will fail if the queue is full
      And by default q_len_wait we are setting more then 1024. so this clause will always be false, unless we alter the q_len_wait from eng cli.

  3. 
      
prajesh
  1. Ship It!
  2. 
      
kdutta
  1. Ship It!
  2. 
      
Loading...