All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Vasilenko <acid@dg.net.ua>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] htb2 -> htb3 problems
Date: Tue, 06 Apr 2004 06:46:37 +0000	[thread overview]
Message-ID: <20040406064637.GA11110@dg.net.ua> (raw)
In-Reply-To: <20040406061635.GA3453@dg.net.ua>

devik (devik@cdi.cz) wrote:
> > I need to switch from htb2 to htb3, because of speed issues (for me,
> > htb2 is unable to handle more then 100mbit duplex with ~550 classes),
> > kernel profiling shows htb_dequeue_prio at 1st place with 3x isolation.
> >
> > So, I've moved from 2.4.19 to 2.4.25 kernel (hi-pac for classification/marking
> > and htb3 for queueing), and traffic rate drop from 100 to 20mbit.
> >
> > What can be wrong? The only change I see is htb2 -> htb3
> 
> Hello,
> 
> I suppose the drop you see is CPU bound ? Did you profiled it
> again ?

No, CPU is about times more in idle state in htb3, and 
5x lowest data rate. AFAIK, htb3 scheduler is faster, so that is the
reason of moving to htb3. 

> Both HTB algorithms are very different  so that one can expect
> different behavior with different data/rules. But I can admit
> that this 5x drop is rather big and unfortunate.

any ideas?

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

  parent reply	other threads:[~2004-04-06  6:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-06  6:16 [LARTC] htb2 -> htb3 problems Michael Vasilenko
2004-04-06  6:33 ` devik
2004-04-06  6:46 ` Michael Vasilenko [this message]
2004-04-06  7:15 ` devik
2004-04-06 11:53 ` Michael Vasilenko
2004-04-06 11:55 ` Michael Vasilenko
2004-04-06 12:02 ` devik
2004-04-06 12:56 ` Michael Vasilenko
2004-04-06 13:06 ` devik
2004-04-06 13:27 ` Michael Vasilenko
2004-04-07  5:51 ` Martin Devera
2004-04-07 10:13 ` Michael Vasilenko

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=20040406064637.GA11110@dg.net.ua \
    --to=acid@dg.net.ua \
    --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.