From: Denys Fedoryschenko <denys@visp.net.lb>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: HTB vs HFSC, HTB is highly inaccurate
Date: Sun, 8 Mar 2009 20:45:39 +0200 [thread overview]
Message-ID: <200903082045.39083.denys@visp.net.lb> (raw)
Hi again
I test again HTB and HFSC, this time in very simple case.
Regarding HTB - i try without quantum, with different values, without and with
cburst (big and small), with HZ=1000 and default, hysteresis on and off - it
is almost same result.
While i set limit at 57, it can reach 61. HFSC results is perfect.
Here is graph snapshopts.
http://www.nuclearcat.com/netdev/htb-problem.png
You can see points where HTB enabled. Other points if HFSC.
Scripts source is:
HTB http://www.nuclearcat.com/netdev/htb-script.txt
HFSC http://www.nuclearcat.com/netdev/hfsc-script.txt
next reply other threads:[~2009-03-08 18:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-08 18:45 Denys Fedoryschenko [this message]
2009-03-09 8:07 ` HTB vs HFSC, HTB is highly inaccurate Jarek Poplawski
2009-03-09 8:18 ` Denys Fedoryschenko
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=200903082045.39083.denys@visp.net.lb \
--to=denys@visp.net.lb \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).