From: Mike Mestnik <cheako911@yahoo.com>
To: lartc@vger.kernel.org
Subject: [LARTC] htb+sfq not being fair, while other methods have better results.
Date: Fri, 12 Jul 2002 23:38:46 +0000 [thread overview]
Message-ID: <marc-lartc-102651717412321@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 1514 bytes --]
I'm running at 290Kbps and I have a cable modem(i'v gotten almost (1.54 * 3)Mbps down).
When I use htb3.6-020525 I get vary sparatic changes(in speed) on my 3 to 7 uploads.
With 7 uploads I should get about 4.5KBits/s, instead I get some much grater and some much less.
I'm using sfq perterb 10.
I'v got a complex setup (View Attachment).
The traffic going to handel 43 is what is not shapping correctly, with no other traffic.
When I tell the app (gtk-gnutella 3.x+my TOS patch) to shape the traffic it dose a better job(self
reporting). Thats where I got the 4.5KBits/s mentioned above, all 7 uploads just solid at
4.xKBits/s
Also there is other data going through that qdisc, I don't see this being a problem thought. See
I continually get SIN packets(all connections accepted but the app) then there is a read, if it
reads an HTTP header OR a gnutella header, it drops saying no open connection(In both cases the
connection get's dropped).
This data should be quite small and NEEDS to be ignored(as background noise), it should be
tolerable!
My first thought is that the drops on the backbone causes there to be A need for a burst of
bandwidth(for the retransmit), is this what the burst setting is for?
I get this idea from MRTG reporting a SOLID line at the htb shaped max. While using the app I get
a wave form.
Please cc me in any reply.
Working Hard on this
Mike
__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com
[-- Attachment #2: qdisc.sh --]
[-- Type: application/x-sh, Size: 3324 bytes --]
reply other threads:[~2002-07-12 23:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-102651717412321@msgid-missing \
--to=cheako911@yahoo.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.