From: Mikael Abrahamsson <swmike@swm.pp.se>
To: linux-mm@kvack.org, linux-raid@vger.kernel.org
Subject: mdraid write performance in different kernels up to 3.0, 3.0 shows huge improvement
Date: Tue, 8 Nov 2011 10:28:57 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.00.1111081019010.19721@uplift.swm.pp.se> (raw)
Hello.
I have been running mdraid->cryptsetup/LUKS->lvm->xfs on Ubuntu AMD64 with
RAID5 and now RAID6 for quite some time, dating back to 2.6.27. Around
2.6.32 I saw quite a bit of regression in write performance (probably the
implementation of barriers), 2.6.35 was acceptable, 2.6.38 was really
really bad, and 3.0 is like a rocket. Best of them all.
I'm talking about 10-20x in different in write performance on my workload,
in combination with the older kernels throwing me page allocation failures
when the write load gets high, and also quite often the machine would just
freeze up and had to be rebooted.
With 2.6.38 I was down to 6-10 megabyte/s write speed, whereas 3.0 seem to
give me 100+ megabyte/s with the exact same workload, I've seen up to 150
megabyte/s writes at good times. This is on a box with AES-NI, so the
crypto is not the limiting factor.
I have from time to time sent out an email regarding my page allocation
failures, but never really got any takers on trying to fault find it, my
tickets with ubuntu also never got any real attention. I haven't really
pushed it super hard with 3.0, but I've thrown loads at it that would make
2.6.38 lock up.
Just wanted to send in this success report that this finally seem to have
seen some really nice improvements!
--
Mikael Abrahamsson email: swmike@swm.pp.se
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2011-11-08 9:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 9:28 Mikael Abrahamsson [this message]
2011-11-09 21:58 ` NeilBrown
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=alpine.DEB.2.00.1111081019010.19721@uplift.swm.pp.se \
--to=swmike@swm.pp.se \
--cc=linux-mm@kvack.org \
--cc=linux-raid@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