Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] QOS problems switching from CBQ to HTB.
Date: Tue, 16 Sep 2003 18:38:36 +0000	[thread overview]
Message-ID: <marc-lartc-106373779402857@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106364615002966@msgid-missing>

On Monday 15 September 2003 23:00, Curtis V. Schleich wrote:
> Trying 4000 right now, I'll try 1500 after I have a chance to see if 4000
> makes any difference.  I have put new commands and stats (which I will
> update periodically over the next few hours) at the
> http://wireless.ccaonline.com/lartc/ site.  On initial examination it does
> not seem to be making any significant difference.  I've still got very
> laggy ping times, which I did not have when we were using CBQ.  During the
> HTB research, I did discover that my CBQ setup was probably weird.  I had a
> class for each user directly off the root, and the total rates FAR exceeded
> the available bandwidth.  So from what I read it was probably pretty
> whacked, but I always seemed to have stable pings under 10ms.  These are
> all over the map (or graph as the case may be).
Can put your cbq setup on your web-server?  So we can compare....

Stef

-- 
stef.coene@docum.org
 "Using Linux as bandwidth manager"
     http://www.docum.org/
     #lartc @ irc.openprojects.net

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2003-09-16 18:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-15 17:14 [LARTC] QOS problems switching from CBQ to HTB Curtis V. Schleich
2003-09-15 18:22 ` Curtis V. Schleich
2003-09-15 20:18 ` Stef Coene
2003-09-15 21:00 ` Curtis V. Schleich
2003-09-15 21:49 ` Steve Wright
2003-09-15 22:00 ` Curtis V. Schleich
2003-09-16 18:38 ` Stef Coene [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-106373779402857@msgid-missing \
    --to=stef.coene@docum.org \
    --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