From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HFSC and prioritization
Date: Fri, 12 May 2006 08:03:00 +0000 [thread overview]
Message-ID: <44644134.2000004@trash.net> (raw)
In-Reply-To: <0633E0EDB4F25F43A2D7179CA11FAFAB25533F@xavier.staff.greatlakes.net>
Alexandru Dragoi wrote:
> I think i'd like more docs in english about hfsc.
Me too. I don't have time to write one myself (and I'm not good at
this), but I can assist if anyone wants to do it.
> I would like to know
> also some tips about scalability at large amount of traffic, like more
> than 100mbit and more than 20kpps. I had a setup one that share 200mbit
> on 2 imq devices(both with a parent class of 200mbit), each with about
> 1000 hfsc classes. About 2 classes with only rt courves, another 2 with
> rt and ls and ul courves, and the rest (end users) with ls and ul
> courves. All only with m2 parametter. And at high traffic packet loss
> appeared. After switching to htb, no more packet loss.
>
> Thanks in advance.
Mhh .. I know of setups where HFSC is running with 10k classes and high
bandwidth (>= 100mbit, don't know the exact amount). When switchting to
rbtrees I made some benchmarks and it performed almost identical to HTB,
so my guess is that its related to IMQ, which still seems to be pretty
broken. It could of course also be a different configuration mistake,
hard to tell without seeing the actual configuration.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-05-12 8:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 17:02 [LARTC] HFSC and prioritization Eliot, Wireless and Server Administrator, Great Lakes Internet
2006-05-11 20:19 ` Jody Shumaker
2006-05-12 5:24 ` Patrick McHardy
2006-05-12 5:31 ` Patrick McHardy
2006-05-12 8:03 ` Patrick McHardy [this message]
2006-05-12 13:33 ` Andy Furniss
2006-05-12 15:30 ` Jody Shumaker
2006-05-12 16:42 ` Patrick McHardy
2006-05-12 16:56 ` Patrick McHardy
2006-05-12 17:49 ` Alexandru Dragoi
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=44644134.2000004@trash.net \
--to=kaber@trash.net \
--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.