All of lore.kernel.org
 help / color / mirror / Atom feed
From: threaded <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] How many (htb) tc classes and qdiscs are too many?
Date: Fri, 03 Jun 2005 02:55:37 +0000	[thread overview]
Message-ID: <429FC6A9.9F1A5BFE@iswest.com> (raw)
In-Reply-To: <000501c567bf$792fd700$650fa8c0@hotsitespencer>

Spencer wrote:
> 
> Is it
> better to create fewer classes and qdisc and assign multiple users to each?
> I haven't been able to find any test on maximum effect number of qdiscs, but
> it could be I have just been looking in the wrong place.  If any one has any
> ideas or could point me in the right direction it would be greatly
> appreciated.
> 
> Spencer

You're not the first person to ask this.  AFAIK there is no benchmark.  People
just do it.  I suggest googling this ML for "hash", "internet cafe",
"pyshaper", "PaceMaker" and whatever else that leads to.  IIRC "hotel" may
also be a good search word.

Tomasz Paszkowski runs a HUGE script for his HFSC setup.

The short answer is that, if you can create a hash that matches, you can
reduce the volume of entries; but that is more a convenience than something
necessary for efficiency.  It takes a HELL of a lot to make Linux groan under
the load.  I once spent > 1 hour loading ~32K filters, but when the script
finished, I could not tell they were there based on the performance of my AMD
Duron 1400 CPU, 256Mb RAM equipped Linux box.

The following is probably the most useful single site you'll find:
http://digriz.org.uk/
--
gypsy
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  reply	other threads:[~2005-06-03  2:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-02 22:07 [LARTC] How many (htb) tc classes and qdiscs are too many? Spencer
2005-06-03  2:55 ` threaded [this message]
2005-06-03  6:37 ` Szymon Miotk
2005-06-03 10:43 ` Konrad
2005-06-03 10:52 ` Paweł Staszewski
2005-06-03 13:57 ` gypsy
2005-06-03 14:19 ` Konrad
2005-06-03 15:10 ` Andy Furniss
2005-06-03 17:39 ` Konrad

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=429FC6A9.9F1A5BFE@iswest.com \
    --to=gypsy@iswest.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.