From: Andy Furniss <adf.lists@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: High latency on HTB class with small packets/high packet rates
Date: Thu, 23 May 2013 20:44:45 +0000 [thread overview]
Message-ID: <519E7FBD.8060904@gmail.com> (raw)
In-Reply-To: <C35D27DA6BA30246B73EC8D145F9F80E1112BC65@exchange1>
Matthew Fox wrote:
> Thanks.
>
> I didn't mention that the rates were already conservative. Our product has an overhead option and for this customer, it was already set to over 20% (ie if we think we have 10 Mbps on our lines, then the qdisc rate would actually only be 8 Mbps).
>
> After some further testing, I was able to get consistently good latency under high UDP packet rates if I just increased that overhead to 40%, which I've never had to do before. It seems like this might be caused by the connections we're using being backed by ATM and requiring to support high rates of small packets, which is an unusual scenario for us- more frequently we'd need to support ATM OR high rates of small packets, but not both.
>
> I'm satisfied with blaming ATM. If anyone else has a better idea, I'd be happy to hear.
In theory you can do atm overheads perfectly see
man tc-stab
In practice you need to also know what fixed overheads there are in
addition to atm and the nature of the device that you are actually
shaping on affects the fixed overhead.
For example, when I had adsl I connected using pppoa/vc mux which gave a
fixed overhead of 10 bytes over ip.
When shaping on ppp directly (PCI dsl card) this was the number to use -
but when shaping on eth (connected to external dsl modem/router) tc
already sees packets as IP +14 so -4 was the overhead to use.
next prev parent reply other threads:[~2013-05-23 20:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 21:24 High latency on HTB class with small packets/high packet rates Matthew Fox
2013-05-22 22:49 ` Matthew Fox
2013-05-23 20:44 ` Andy Furniss [this message]
2013-05-24 17:03 ` Matthew Fox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=519E7FBD.8060904@gmail.com \
--to=adf.lists@gmail.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.