All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philip A. Prindeville" <philipp_subx@redfish-solutions.com>
To: Julien Vehent <julien@linuxwall.info>
Cc: Netdev <netdev@vger.kernel.org>, netfilter <netfilter@vger.kernel.org>
Subject: Re: QoS weirdness : HTB accuracy
Date: Tue, 18 May 2010 18:07:12 -0600	[thread overview]
Message-ID: <4BF32BB0.7010700@redfish-solutions.com> (raw)
In-Reply-To: <067c83163988908ef546d7ff7f560a17@localhost>

On 03/25/2010 12:06 PM, Julien Vehent wrote:
> Hello folks,
>
> I observe unused bandwidth on my QoS policy that I cannot explain.
> Conditions are: I have a HTB tree with 8 classes and a total rate of
> 768kbits. I use the ATM option so I assume the real rate to be something
> close to 675kbits (about 88% of the ethernet rate).
>
> The sum of my 8 rates is exactly 768kbits. Some have ceil values up to
> 768kbits.
>
> When class 20 "tcp_acks" starts borrowing, TC reduces the total bandwidth
> down to 595kbits/S (minus 79kbits/s). And I can't explain why....
>
> The attached graph "tc_htb_weirdness.png" shows the result: there are
> 'holes' in the sending rate. 
>
> I tried to play with burst sizes, r2q value and hysteresis mode, but the
> results are the same.
>
> System is debian squeeze, kernel version is 2.6.26, iproute2 version is
> 2.6.26 - 07/25/2008.
>
> I have attached two files:
> - "tcrules.txt" : the traffic control rules
> - "tc_htb_weirdness.png" : the rrdtool graph, resolution is 1 second.
>
> And here: http://jve.linuxwall.info/ressources/code/tc_hole_analysis.html
> a sheet with some of the measures values. I used it to calculate the size
> of one of the hole. The last table (with green and red cells) shows that,
> when class 20 "tcp_acks" starts sending at unixtime 1265496813, there is a
> lot of bandwidth left over (last column is all green). During the 95
> seconds while class 20 is sending, 3880776 bits could be sent but are not.
> That's about 40kbits/s on average. 
>
> Does anybody observess the same behavior? Any logical explanation to this
> or is it a bug ?
>
>
> Julien

Sorry for the late response:  could this be an "aliasing" issue caused
by sampling intervals (granularity)?

-Philip


  parent reply	other threads:[~2010-05-19  0:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25 18:06 QoS weirdness : HTB accuracy Julien Vehent
2010-03-25 18:31 ` Marek Kierdelewicz
2010-03-25 19:17   ` Julien Vehent
2010-03-25 19:36     ` Marek Kierdelewicz
2010-03-25 21:50       ` Julien Vehent
     [not found] ` <A846BBAEAA674FAA90FA2008DDD1ED12@hakkenden>
2010-03-25 21:49   ` Julien Vehent
     [not found]     ` <F44DB77B8BA04D108C884E966BD65F9E@hakkenden>
2010-03-25 22:15       ` Julien Vehent
2010-05-19  0:07 ` Philip A. Prindeville [this message]
2010-05-22 14:29   ` Julien Vehent
2010-06-10 21:22     ` Andrew Beverley
2010-07-04 17:50       ` Andrew Beverley
2010-07-07 13:07         ` Jesper Dangaard Brouer
2010-07-07 15:07           ` Jussi Kivilinna
2010-08-11 17:59             ` Andrew Beverley
2010-08-14 17:27               ` Jussi Kivilinna
2010-08-11 14:27           ` Andrew Beverley
2010-07-07 12:50     ` Jesper Dangaard Brouer
2010-07-07 11:40 ` Jesper Dangaard Brouer

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=4BF32BB0.7010700@redfish-solutions.com \
    --to=philipp_subx@redfish-solutions.com \
    --cc=julien@linuxwall.info \
    --cc=netdev@vger.kernel.org \
    --cc=netfilter@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.