General list for discussing Bufferbloat
 help / color / mirror / Atom feed
* [Bloat] Any aqm evaluation at speeds >=10Gbit/s?
@ 2015-05-19 13:04 Bless, Roland (TM)
  2015-05-19 21:00 ` Alan Jenkins
  0 siblings, 1 reply; 2+ messages in thread
From: Bless, Roland (TM) @ 2015-05-19 13:04 UTC (permalink / raw)
  To: aqm, bloat

Hi,

has anyone recently tested AQMs like Codel or PIE
at speeds of >=10Gbit/s? If so, where are the results available?
Pointers greatly appreciated...

Regards,
 Roland

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [Bloat] Any aqm evaluation at speeds >=10Gbit/s?
  2015-05-19 13:04 [Bloat] Any aqm evaluation at speeds >=10Gbit/s? Bless, Roland (TM)
@ 2015-05-19 21:00 ` Alan Jenkins
  0 siblings, 0 replies; 2+ messages in thread
From: Alan Jenkins @ 2015-05-19 21:00 UTC (permalink / raw)
  To: bloat; +Cc: aqm

On 19/05/15 14:04, Bless, Roland (TM) wrote:
> Hi,
>
> has anyone recently tested AQMs like Codel or PIE
> at speeds of >=10Gbit/s? If so, where are the results available?
> Pointers greatly appreciated...
>
> Regards,
>   Roland

I know only background information on that.

1) fq_codel was written by Eric Dumazet of Google and tested at 10G. 
Allegedly at 10G CoDel works fine, and fq_codel costs "2% of a single 
modern CPU core".  Sounds trustworthy but that doesn't give you any 
details :).  Cite: Jim Gettys.

Codel: 
https://gettys.wordpress.com/2012/05/22/a-milestone-reached-codel-is-in-linux/
fq_codel: https://www.ietf.org/proceedings/87/slides/slides-87-aqm-6.pdf


[Whether router queue management can achieve anything for a 10g link 
which also has high multiplexing and 50%+ exponential 'slow start' with 
IW10...  I think we didn't have an answer ready when that came up.]


2) Eric also wrote sch_fq and tested it at 10G.  sch_fq is only designed 
for end hosts and is not designed or implemented to reduce latency AIUI.


[I may finally understand this article

https://lwn.net/Articles/564978/

For our bufferbloat at the ISP network edge, the more important part of 
the article is TSO sizing.  Which does not depend on qdisc.

sch_fq just does TCP pacing (and flow queuing).

sch_fq pacing doesn't affect slow start _or_ saturating ("ack clocked") 
flows, which are the causes of edge bufferbloat.  It could do, but 
Eric's next priority is to improve TCP congestion control.

https://lists.bufferbloat.net/pipermail/bloat/2015-April/002797.html
https://lists.bufferbloat.net/pipermail/bloat/2015-April/002801.html]

What does sch_fq actually pace?  Well, "you no longer have to
slow start after idle", so it should help things like re-used HTTP 
connections.  But I think the implication is also for consistent flows 
that don't saturate: media streaming.

https://lists.bufferbloat.net/pipermail/bloat/2015-April/002764.html]


Alan


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-05-19 21:01 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-05-19 13:04 [Bloat] Any aqm evaluation at speeds >=10Gbit/s? Bless, Roland (TM)
2015-05-19 21:00 ` Alan Jenkins

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox