From: Taylor Lewick <taylor.lewick@gmail.com>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Increased Latencies when upgrading kernel version
Date: Thu, 1 Apr 2010 14:12:57 -0500 [thread overview]
Message-ID: <o2vd585dc4f1004011212s65cc2beewed2f19321210a249@mail.gmail.com> (raw)
For some time now we've been running an older kernel, 2.6.16.60. When
we tried to upgrade, first going to 2.6.27.19 and then to 2.6.32.1 and
2.6.33.1 we noticed that latencies increased. At first we noticed it
by doing network tests via udpping, netperf, etc. We made some
tweaks, and were able to get network latency to within 1 to 2
microseconds of where we were previously on 2.6.16.60. Then we did
some more testing, and noticed that system latency also seems higher.
We've done our tests on identical hardware servers, same NICs,
connected through same network gear. Basically, we've tried to keep
everything identical except the kernel versions, and we are unable to
achieve the same performance for system latency on the newer kernels,
despite adjusting various kernel settings and recompiling.
The latency differences are about 15 microseconds per transaction.
At this point, I don't know what else to try. I haven't played around
with the /proc/sys/kernel/sched_* paramaters under the newer kernels
yet. Have tried changing pre-emption modes with little effect, in
fact, voluntary preemption seems to be peforming the best for us.
At this time the realtime patch isn't really an option for us to
consider, at least not yet.
Any suggestions? Is this a known issue when upgrading to more recent
kernel versions?
Thanks,
Taylor
next reply other threads:[~2010-04-01 19:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 19:12 Taylor Lewick [this message]
2010-04-01 21:19 ` Increased Latencies when upgrading kernel version Eric Dumazet
2010-04-02 1:53 ` Taylor Lewick
2010-04-05 17:34 ` Taylor Lewick
2010-04-06 14:10 ` Xianghua Xiao
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=o2vd585dc4f1004011212s65cc2beewed2f19321210a249@mail.gmail.com \
--to=taylor.lewick@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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).