From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: XFS Test Results Interpretation
Date: Mon, 25 Oct 2010 16:06:16 +0200 [thread overview]
Message-ID: <201010251606.16653@zmi.at> (raw)
In-Reply-To: <4CC5894D.6090409@hardwarefreak.com>
[-- Attachment #1.1: Type: Text/Plain, Size: 985 bytes --]
On Montag, 25. Oktober 2010 Stan Hoeppner wrote:
> > Kernel: 2.6.18-128.el5
>
> You need a much newer kernel. 2.6.18 is ancient released in 2006,
> though CentOS have patched the bejesus out of it--128 times.
Oh, I didn't look at that.
2.6.18 is a performance killer compared to an actual 2.6.36 kernel.
There's been so much work in between. If you can, try a 2.6.36 and
compare your performance. Everything will be a lot faster than with
2.6.18. You don't need to fiddle with mkfs/mount options, just upgrade
the kernel and without any other tuning you will be much faster than
before.
--
mit freundlichen Grüssen,
Michael Monnerie, Ing. BSc
it-management Internet Services
http://proteger.at [gesprochen: Prot-e-schee]
Tel: 0660 / 415 65 31
****** Radiointerview zum Thema Spam ******
http://www.it-podcast.at/archiv.html#podcast-100716
// Wir haben im Moment zwei Häuser zu verkaufen:
// http://zmi.at/langegg/
// http://zmi.at/haus2009/
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
[-- Attachment #2: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-10-25 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 11:17 XFS Test Results Interpretation Andrew Debenham
2010-10-25 11:51 ` Michael Monnerie
2010-10-25 13:42 ` Stan Hoeppner
2010-10-25 14:06 ` Michael Monnerie [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-24 2:59 Andrew Debenham
2010-10-24 3:38 ` Stan Hoeppner
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=201010251606.16653@zmi.at \
--to=michael.monnerie@is.it-management.at \
--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