From: Michael Guntsche <mike@it-loops.com>
To: Maurice Hilarius <maurice@harddata.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: Severe slowdown with LVM on RAID, alignment problem?
Date: Fri, 29 Feb 2008 08:37:44 +0100 [thread overview]
Message-ID: <13b69e90155ddee52ada8df5a5ec416c@localhost> (raw)
In-Reply-To: <47C75436.9010301@harddata.com>
On Thu, 28 Feb 2008 17:39:18 -0700, Maurice Hilarius <maurice@harddata.com>
wrote:
> If you use bonnie++ with a file size of 1GB, I hope you only have 256MB
> of RAM in this machine.
> Otherwise buffering will horribly skew any results to the point that
> they are unusable
Thank you for the info.
Currently I have 512MB RAM and 500MB SWAP in this box. I upped the size to
8GB, so 8 files a 1GB are created.
While the result for XFS is different, reading is actually faster, the
differnece between xfs and xfs on lvm is still there.
pvcreate was called so that the first PE starts exactly at 256K, no sunits
where used with mkfs.xfs for the lvm case.
I still do not understand the read output at all.
Version 1.03c ------Sequential Output------ --Sequential Input-
--Random-
-Per Chr- --Block-- -Rewrite- -Per Chr- --Block--
--Seeks--
Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec
%CP
xfs 8G 38876 25 28244 22 103891 40
161.4 2
lvm-al 8G 37089 24 18821 23 48489 40 155.8
2
While it looks like that writing is actually pretty similar reading is
still way down.
Totally at loss here,
Michael
next parent reply other threads:[~2008-02-29 7:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47C75436.9010301@harddata.com>
2008-02-29 7:37 ` Michael Guntsche [this message]
2008-02-29 8:12 Severe slowdown with LVM on RAID, alignment problem? Michael Guntsche
2008-02-29 10:37 ` Peter Rabbitson
2008-02-29 10:45 ` Michael Guntsche
2008-03-01 20:45 ` Bill Davidsen
2008-03-01 21:26 ` Michael Guntsche
2008-03-02 20:14 ` Bill Davidsen
-- strict thread matches above, loose matches on Subject: below --
2008-02-29 0:05 Michael Guntsche
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=13b69e90155ddee52ada8df5a5ec416c@localhost \
--to=mike@it-loops.com \
--cc=linux-raid@vger.kernel.org \
--cc=maurice@harddata.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).