From: Anton A Vorobev <anton.vorobev@firma.seznam.cz>
To: xfs@oss.sgi.com
Subject: Slow seek in kernels >= 2.6.18
Date: Thu, 18 Oct 2007 10:12:28 +0200 [thread overview]
Message-ID: <4717156C.3030308@firma.seznam.cz> (raw)
Hi!
A question. We've got an application that runs about 30-40 minutes.
After kernel upgrade from 2.6.17 branch, it runs about 3 hours.
I've made tests with the help of bonnie++, it shows that random seek
operations are about 3 times slower in kernels newer than 2.6.18 in
comparison with 2.6.17. This difference may be seen only during high
load of a server. When it is in normal state, parameters are rather the
same.
We use XFS filesystem. Does any one know may it be because of upgrade of
XFS driver in kernel? Any ideas?
Thanks a lot.
______________________________________________________________
Anton Vorobev
Programátor
Seznam.cz, a.s. Radlická 608/2 150 00 Praha 5
tel.: +420 234 694 706
fax: +420 234 694 115
anton.vorobev@firma.seznam.cz
http://www.seznam.cz
next reply other threads:[~2007-10-18 8:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 8:12 Anton A Vorobev [this message]
2007-10-18 10:15 ` Slow seek in kernels >= 2.6.18 Bhagi rathi
2007-10-18 18:21 ` {WHAT?} " Peter Grandi
2007-10-24 0:37 ` Josef Sipek
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=4717156C.3030308@firma.seznam.cz \
--to=anton.vorobev@firma.seznam.cz \
--cc=xfs@oss.sgi.com \
/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