[Codel] question about "data center" models

[Andrew McGregor]

A normal configuration is more like a 300 microsecond RTT with early marking RED and/or switches configured to backpressure sources with fairly short queues.

There may be enormous amounts of buffer in a switch, but it is usually divided among a rather large number of queues (ingress and egress queues per port, plus perhaps several in the forwarder).

Data center operators are very concerned about latency because in most cases the metric they are tracking is the completion time of the last short flow to complete in a transaction (that will be composed of, say, 20-odd 500kB or thereabouts TCP connections).  There is often a hard time limit on transaction components; one I've heard of is that all data for a query must be at the aggregation node in 8ms, or it will be dropped and the query result quality will go down.

On 4/05/2012, at 11:23 AM, Kathleen Nichols wrote:

> 
> So, I thought I'd see what happens with a 1G bottleneck and a 5ms RTT.
> I'm still checking
> it out, but I thought I'd try to understand the concern.  So, under a
> constant heavy load,
> codel will accept a 5ms standing queue. I got the impression this was a
> concern. I'm
> not exactly certain why. How much buffer is normally in the bottleneck?
> If it's enough
> for a "nominal" RTT of 100 ms, with drop tail it will just fill up and
> stay there under
> load. So, 100ms of delay. If it's at a RTT of 5ms, then the buffer will
> fill up and give 5ms
> of delay without any ability to absorb bursts.  What is the normal
> configuration?
> 
> 	Kathie
> _______________________________________________
> Codel mailing list
> Codel at lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/codel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2330 bytes
Desc: not available
URL: <https://lists.bufferbloat.net/pipermail/codel/attachments/20120504/2c6b409d/attachment-0002.bin>