Raja Subramanian a825661aff Use weighted loss to detect loss based congesiton signal. (#3169) ...

* Use weighted loss to detect loss based congesiton signal.

- Increase JQR min loss to 0.25.
- Use weighted loss ratio so that more packet rate gets higher
  weightage. At default config, 10 packets in 1/2 second will form a
  valid packet group for loss based congestion signal consideration. Two
  packets lost in that group may not be bad. So, bumped up the
  JQR min loss to 0.25. However, 20% loss (or even much lesser loss)
  could be problematic if the packet rate is higher (potentially
  multiple streams affected and there could be a lot of NACKs as a result).
  So, weight it by packet rate so that higher packet rates enter JQR
  at lower losses.

* WIP

* use aggregated loss

2024-11-12 09:21:28 +05:30

..

congestion_detector.go

Use weighted loss to detect loss based congesiton signal. (#3169)

2024-11-12 09:21:28 +05:30

packet_group.go

Use weighted loss to detect loss based congesiton signal. (#3169)

2024-11-12 09:21:28 +05:30

packet_info.go

Use weighted loss to detect loss based congesiton signal. (#3169)

2024-11-12 09:21:28 +05:30

packet_tracker.go

Use weighted loss to detect loss based congesiton signal. (#3169)

2024-11-12 09:21:28 +05:30

send_side_bwe.go

Use weighted loss to detect loss based congesiton signal. (#3169)

2024-11-12 09:21:28 +05:30

traffic_stats.go

Use weighted loss to detect loss based congesiton signal. (#3169)

2024-11-12 09:21:28 +05:30

twcc_feedback.go

Use weighted loss to detect loss based congesiton signal. (#3169)

2024-11-12 09:21:28 +05:30