From: Josef Sipek <jsipek@fsl.cs.sunysb.edu>
To: Anton A Vorobev <anton.vorobev@firma.seznam.cz>
Cc: xfs@oss.sgi.com
Subject: Re: Slow seek in kernels >= 2.6.18
Date: Tue, 23 Oct 2007 20:37:06 -0400 [thread overview]
Message-ID: <20071024003706.GA27516@filer.fsl.cs.sunysb.edu> (raw)
In-Reply-To: <4717156C.3030308@firma.seznam.cz>
On Thu, Oct 18, 2007 at 10:12:28AM +0200, Anton A Vorobev wrote:
> 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.
I think that's about when the defaults for few /proc/sys/vm/ vars changed.
One from 10 to 5, and another from 40 to 10. I forget the exact filenames.
Josef 'Jeff' Sipek.
--
Once you have their hardware. Never give it back.
(The First Rule of Hardware Acquisition)
prev parent reply other threads:[~2007-10-24 1:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-18 8:12 Slow seek in kernels >= 2.6.18 Anton A Vorobev
2007-10-18 10:15 ` Bhagi rathi
2007-10-18 18:21 ` {WHAT?} " Peter Grandi
2007-10-24 0:37 ` Josef Sipek [this message]
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=20071024003706.GA27516@filer.fsl.cs.sunysb.edu \
--to=jsipek@fsl.cs.sunysb.edu \
--cc=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