PolarisX wrote:I'm on Cox 300/30 plan. I get about 400 down with a SB6183 and can use SQM under FQ_CODEL (simplest.qos) full speed. CAKE choked about about 160 ish. Late at night I will actually see momentary bursts into the mid 500s.
I'm only using it on upstream at the moment, its very rare we saturate the WAN link here. Took almost all of my upstream bufferbloat away. This is the most asymmetric link I've ever used, by far.
A SB6141 will be tough on a node, but if you are getting 300 with a SB6141 it must not be as busy of a node.
Wow, can't believe you are getting 400-500+ on Cox's 300/30 plan. Is that sustained downloads or only for a 10-20 second burst at the beginning of a download? If its sustained, that makes me think that since 300/30 is their fastest plan, they uncap the modem for those who have it. I would upgrade my modem, but with Cox rolling out either DOCSIS 3.1 or GigaBlast (FTTN) to basically all their service areas in the next year, I don't want to waste my money buying a DOCSIS 3.1 modem now, and then wind up getting GigaBlast in my neighborhood instead. I get the full 300/30 on my SB6141, but no more than that. From your experience, I'm sure I could get more with a 16 channel modem, but since the only reason I even have their 300/30 plan is they are giving to me for $5/month less than the regular price of their 50/5 plan for 12 months for being a long-time customer, I'm plenty happy and hardly ever come close to using 300mbps down anyway (hence why I had been on their 50/5 plan for years, back since it was 25/5, and before that 10/2, and going way back to 1999, 5/0.5). I had upgraded to my SB6141 just about 2-3 years ago when they bumped the speed to 50/5 because my old DOCSIS 2.0 modem from 1999 maxed out around 33mbps. I had been getting 60/6 on their 50/5 plan with my SB6141.
Back on topic, so it is CAKE that chokes at 150-160mbps, not SQM or the router, thanks for the info! I wonder why that is -- if it's a bug or if the way it works requires much more processing power. Since Cox has minimal to no buffer-bloat on the downstream, I'll stick with CAKE for now, since I have the downstream set at 0 and it works great for me like that, practically no buffer-bloat on the downstream to begin with and CAKE takes away practically all buffer-bloat from the upstream, always score an A or A+ on DSLReports' test.
(Last edited by starcms on 4 Sep 2017, 07:27)