All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB Script
Date: Fri, 26 Nov 2004 22:28:17 +0000	[thread overview]
Message-ID: <41A7AE01.6020206@dsl.pipex.com> (raw)
In-Reply-To: <41A5065C.8060304@wp.pl>

Lenthir wrote:
> Hi everybody!
> 
> I wrote nice script, but I need some help....
> Script is working almost well.
> 
> My question is:
> Can I minimalize PING time more than this script can? (nowadays is 
> 70-150ms with large load of link)
> My first problem is - unreal big PING on router, and almost excellent 
> (nowadays is 70-150ms) PING on computers in network.
> 
> My users don't complain, but I noticed that the pages is becoming load 
> quickly and when it's almost done.. the transfer is going down!!
> And second symptom is: when I open pages PING grows to 800ms, and 
> quickly go down. It's almost imperceptible, but it happens.
> What's wrong? All packets is going to correct pipes. What should I do more?
> I suspect, that time of change of speed (HTB's reaction time) many 
> queues is long. How can I improve this?

It's a big script - I only looked briefly and may have missed things.

Shaping inbound traffic from the wrong end of the bottleneck is hard, 
HTB would need to be predictive to do it better.

For SFQ you can change queue length (SFQ_DEPTH) in net/sched/sch_sfq.c 
or you could use esfq and choose length with options.

How many users do you have?

If you have 2mbit link then I think you need to reduce the ceils or you 
won't have a queue to shape with.

> Script is very nice, but I need some professional help and advices.
> 
> Everything You can check when script is working:
> ./htb0.5.3en stat <IP> (example: ./htb0.5.3en stat 192.168.0.2)
> ./htb0.5.3en stat lan
> ./htb0.5.3en stats
> 
> My network's statistics:
> http://stats.opat.hopto.org/
> http://stats.zabierzow.net/
> 
> I attached my script. IMQ with imq_nat.diff patch is required (or AB 
> option in kernels 2.6), patched iptables(IMQ patch) is required, iproute 
> is required and bc is required. I tested this script on 2.6.9 kernel and 
> iproute from .deb package.
> 
> And second less important problem... How Can I mark squid's MISS 
> packets? Is Debian's Squid Package patched to change TOS?
> http://stats.zabierzow.net/squid.php :d

I assume a miss is traffic squid gets from the net, if unshaped this 
will make you go overlimits - so is not neccessarily just a secondary 
problem.


If you are NATing and have IMQ hooking after NAT in PREROUTING then 
traffic headed for squid will still have your real IP and forwarded 
local IP. You need to use u32 to seperate it.

Andy.

> Someone will help?


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

  parent reply	other threads:[~2004-11-26 22:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-24 22:08 [LARTC] HTB Script Lenthir
2004-11-25 20:08 ` Lenthir
2004-11-26 22:28 ` Andy Furniss [this message]
2004-11-27 12:17 ` Lenthir
2004-11-29 22:30 ` Andy Furniss
2004-12-08 10:27 ` Lenthir
2005-01-08  9:25 ` [LARTC] htb script jayesh
2005-01-17  0:17 ` Andy Furniss

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=41A7AE01.6020206@dsl.pipex.com \
    --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 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.