lilstone87
Very Senior Member
Well I have spent a couple hours on both CakeQoS, and FlexQoS today. I feel both are pretty damn good right now.
For me, I am leaning towards Flex QoS. As it works with Adaptive QoS, and more info is available to the user with it. Plus the custom rules that can be applied. Also with me having gigabit internet, I am able to get a little more out of downstream speed. There's one negative with using it, and I think most will know this already, and it's one of the main reasons, a lot of you are interested in using CakeQoS. That upload latency.
With CakeQoS, running a fast.com test. Over several tests, my loaded upstream latency average between 16-24ms. With FlexQoS, using FQ_Codel, upstream loaded latency, average between 56-62ms. Which overall is a pretty decent sized jump in latency. So it will be a harder choice to make for some of us.
My overall hope is.. one day Cake can be included for use with Adaptive QoS, if possible. Because I would for sure trade a bit of downstream speed, to use Cake.
For me, I am leaning towards Flex QoS. As it works with Adaptive QoS, and more info is available to the user with it. Plus the custom rules that can be applied. Also with me having gigabit internet, I am able to get a little more out of downstream speed. There's one negative with using it, and I think most will know this already, and it's one of the main reasons, a lot of you are interested in using CakeQoS. That upload latency.
With CakeQoS, running a fast.com test. Over several tests, my loaded upstream latency average between 16-24ms. With FlexQoS, using FQ_Codel, upstream loaded latency, average between 56-62ms. Which overall is a pretty decent sized jump in latency. So it will be a harder choice to make for some of us.
My overall hope is.. one day Cake can be included for use with Adaptive QoS, if possible. Because I would for sure trade a bit of downstream speed, to use Cake.