Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Need help with HTB
Date: Wed, 29 Oct 2003 00:32:15 +0000	[thread overview]
Message-ID: <marc-lartc-106738913704946@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106729452827597@msgid-missing>

On Monday 27 October 2003 10:37 pm, Mihai Tanasescu wrote:
> Hello,
>
>  1.
>
>  I currently have a 128kbps cable link to the internet..and I'm sharing
>  this connection with others.

<snip>

>  I have the same problem with a htb script on an adsl connection (with
>  the htb script I get ping response times of 80-90..without it I get
>  200-300 ms...but these response times aren't very stable..it's
> something
>  like I'm getting 40 ms..then 100 ms..then 50 ms..)

I am a newbie and don't yet fully understand the HTB stuff, but have 
experimented with others scripts/programs and thought about QOS for 
latency - which is what I will be aiming for when my home network is 
eventually finished.

With an uplink of 128000 and MTU 1500 then you would expect this behavior 
as a 1500 byte packet will take >90ms to get up the wire. Reducing MTU 
should help, also quantum/burst should be small enough to release only one 
packet - I notice some big quantums in your other mail. I don't know about 
cable, but with dsl some MTUs are more efficient than others - which are 
best depends on whether your dsl uses pppoa or pppoe etc.

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

      parent reply	other threads:[~2003-10-29  0:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-27 22:37 [LARTC] Need help with HTB Mihai Tanasescu
2003-10-28 18:12 ` Stef Coene
2003-10-28 20:38 ` Mihai Tanasescu
2003-10-28 21:05 ` Stef Coene
2003-10-29  0:32 ` Andy Furniss [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-106738913704946@msgid-missing \
    --to=andy.furniss@dsl.pipex.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