From: Ciprian Nica <htb@nimaci.pcnet.ro>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB - problem with one thread
Date: Thu, 29 Aug 2002 08:19:08 +0000 [thread overview]
Message-ID: <marc-lartc-103060924816719@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103054061315522@msgid-missing>
On Wednesday 28 August 2002 20:45, Stef Coene wrote:
> > The problem is that clients can have their bandwidths at maximum only if
> > they use a download accelerating software like DAP with multiple
> > symultanous threads. Using only one thread, a single download can reach
> > about 60% of the allocated bandwidth.
>
> Quantum is used if 2 or more classes with the same parent are fighting for
> bandwidth. First, they are allowed to get the rate you gave them. For the
> remaining bandwidth, quantum is used. Each class may send quantum bytes.
> You have to make sure quantum > MTU (typical 1500 bytes for ethernet).
>
> What if you use no sfq qdiscs?
>
> Stef
I have tried with pfifo queues and it's the same. I made many tests changing
quantum, queueing for leaf but in no case I could reach the allocated
bandwidth with a single download thread. The same limit set on cisco router
with traffic-shape, worked fine.
Could there be a problem when there are many qdiscs ? Are there many
calculations to be done, so the packets get delayed and the TCP transfer rate
is lowered.
Ciprian
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-08-29 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 13:15 [LARTC] HTB - problem with one thread Ciprian Nica
2002-08-28 17:45 ` Stef Coene
2002-08-29 8:19 ` Ciprian Nica [this message]
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=marc-lartc-103060924816719@msgid-missing \
--to=htb@nimaci.pcnet.ro \
--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.