From: Sonny <smaniaol@gmail.com>
To: netdev@vger.kernel.org
Subject: Kernel 2.4 vs 2.6 Traffic Controller Performance
Date: Wed, 3 Oct 2007 08:30:02 +0800 [thread overview]
Message-ID: <9dbec86d0710021730g2cfaeb16o7057700b970f7e8d@mail.gmail.com> (raw)
Hello
I hope this is the right place to ask this.Does any know if there is a
substantial difference in the performance of the traffic controller
between kernel 2.4 and 2.6. We tested it using 1 iperf server and use
250 and 500 clients, altering the burst. We use the top command to
check the idle time of our router to see this. The results we got from
the 2.4 kernel shows around 65-70% idle time while the 2.6 shows
60-65% idle time. We tried to use MRTG and we're not getting any
results either. We want to know if we could improve the bandwidth by
upgrading the kernel, else we would have to get a new bandwidth
manager. Could anyone have the similar test regarding this or suggest
a better way to do this. Thanks in advance.
next reply other threads:[~2007-10-03 0:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 0:30 Sonny [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-03 6:14 kernel 2.4 vs 2.6 Traffic Controller performance Sonny
2007-10-03 7:00 ` Eric Dumazet
2007-10-03 8:31 ` Sonny
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=9dbec86d0710021730g2cfaeb16o7057700b970f7e8d@mail.gmail.com \
--to=smaniaol@gmail.com \
--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).