From: Dominik Brodowski <linux@dominikbrodowski.net>
To: linux-raid@vger.kernel.org, xfs@oss.sgi.com,
linux-kernel@vger.kernel.org
Subject: How to track down abysmal performance ata - raid1 - crypto - vg/lv - xfs
Date: Wed, 4 Aug 2010 09:35:46 +0200 [thread overview]
Message-ID: <20100804073546.GA7494@comet.dominikbrodowski.net> (raw)
Hey,
on a production system I run kernel 2.6.35 and
XFS (rw,relatime,nobarrier)
on a
lvdevice of a vgroup
consisting of five
dm-crypt devices (cryptsetup -c aes-lrw-benbi -s 384 create)
, each of which runs on a
md-raid1 device (mdadm --create --level=raid1 --raid-devices=2)
on two
750 GB ATA devices.
The read performance is abysmal. The ata devices can be ruled out, as hdparm
resulted in acceptable performance:
> Timing cached reads: 9444 MB in 2.00 seconds = 4733.59 MB/sec
> Timing buffered disk reads: 298 MB in 3.02 seconds = 98.73 MB/sec
How can I best track down the cause of the performance problem,
a) without rebooting too often, and
b) without breaking up the setup specified above (production system)?
Any ideas? perf(1)? iostat(1)?
Thanks & best,
Dominik
next reply other threads:[~2010-08-04 7:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 7:35 Dominik Brodowski [this message]
2010-08-04 8:50 ` How to track down abysmal performance ata - raid1 - crypto - vg/lv - xfs Christoph Hellwig
2010-08-04 9:13 ` Dominik Brodowski
2010-08-04 9:21 ` Christoph Hellwig
2010-08-04 9:16 ` Michael Monnerie
2010-08-04 10:25 ` Dominik Brodowski
2010-08-04 11:18 ` Christoph Hellwig
2010-08-04 11:24 ` Dominik Brodowski
2010-08-04 11:53 ` Mikael Abrahamsson
2010-08-04 12:56 ` Mike Snitzer
2010-08-04 22:24 ` Neil Brown
[not found] ` <20100804111803.GA32643__39273.3621680692$1280923964$gmane$org@infradead.org>
2010-08-04 17:43 ` Andi Kleen
2010-08-04 20:33 ` Valdis.Kletnieks
2010-08-05 9:31 ` direct-io regression [Was: How to track down abysmal performance ata - raid1 - crypto - vg/lv - xfs] Dominik Brodowski
2010-08-05 11:32 ` Chris Mason
2010-08-05 12:36 ` Josef Bacik
2010-08-05 15:35 ` Dominik Brodowski
2010-08-05 15:39 ` Chris Mason
2010-08-05 15:53 ` Dominik Brodowski
2010-08-05 16:35 ` Dominik Brodowski
2010-08-05 20:47 ` Performance impact of CONFIG_DEBUG? direct-io test case Dominik Brodowski
2010-08-05 20:54 ` Performance impact of CONFIG_SCHED_MC? " Dominik Brodowski
2010-08-05 18:58 ` direct-io regression [Was: How to track down abysmal performance ata - raid1 - crypto - vg/lv - xfs] Jeff Moyer
2010-08-05 19:01 ` Chris Mason
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=20100804073546.GA7494@comet.dominikbrodowski.net \
--to=linux@dominikbrodowski.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).