From: Adrian Chung <adrian-lartc@enfusion-group.com>
To: lartc@vger.kernel.org
Subject: [LARTC] WonderShaper and NNTP traffic.
Date: Tue, 25 Nov 2003 11:23:13 +0000 [thread overview]
Message-ID: <marc-lartc-106975950508790@msgid-missing> (raw)
Hi!
I'm testing out the wshaper script using both CBQ and HTB, with:
DOWNLINK\x1152
UPLINK12
DEV=eth3
It works great for simultaneous uploads/downloads, and FTP traffic,
but when I enable wshaper and am doing an NNTP download, it slows NNTP
downloads to 50kB/s. When I do a 'wshaper stop', NNTP downloads creep
back up to about 150kB/s.
FTP downloads, as mentioned go full speed at around ~130-140kB/s as
well.
Any ideas on why this might be happening, or what I can try to tweak?
--
Adrian Chung (adrian at enfusion-group dot com)
http://www.enfusion-group.com/~adrian/
GPG Fingerprint: C620 C8EA 86BA 79CC 384C E7BE A10C 353B 919D 1A17
[rogue.genosha.enfusion-group.com] 5:10pm up 18 days, 1:17, 5 users
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2003-11-25 11:23 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-106975950508790@msgid-missing \
--to=adrian-lartc@enfusion-group.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox