disable hysteria brutal algo?

[VendettaReborn]

context

XTLS/Xray-core#3547

key

"大家能一起换到 BBR、一起提升体验，而大家一起 Brutal 就会炸。Brutal 并不是传统的拥塞控制，本质上是抢占带宽"

thoughts

shall we disable hysteria Brutal algorithm by some feature gate, or just delete the Brutal part of the code?

[Itsusinn]

Client's Congestion Controller doesn't affect too much to the Network, because it only affects uplink bandwidth

[VendettaReborn]

more contexts: 可恶的 TCP 加速

[VendettaReborn]

i think the point is, if we think brutal is bad(to me, that's a fact), should we hand the option to clash-rs's users?

[Itsusinn]

more contexts: 可恶的 TCP 加速

In that theory, BBR is just as bad as Brutal (

[VendettaReborn]

maybe, but the main purpose of this issue is to raise the discussion. better to remain a debate than integrating the BBR/Brutal into project without considering this moral concerns.

[ibigbug]

There's successful examples using BBR for broader internet https://aws.amazon.com/blogs/networking-and-content-delivery/tcp-bbr-congestion-control-with-amazon-cloudfront/

BBR responds more agilely to changing conditions, but continues to aggressively attempt to transmit as much data as possible even when there are transient issues.

I'm not sure if Brutal does slow down in the case condition gets worse, it seems BBR does that in certain case?

[ibigbug]

there's BBRv2 which seems address some of the concerns https://datatracker.ietf.org/meeting/105/materials/slides-105-iccrg-bbr-v2-a-model-based-congestion-control