All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rudolph Bott <rb@megabit.net>
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM / 3ware performance
Date: Wed, 17 Dec 2008 15:26:46 +0000 (UTC)	[thread overview]
Message-ID: <26617199.341229527604820.JavaMail.rudi@toronto> (raw)
In-Reply-To: <8251455.241229524675229.JavaMail.rudi@toronto>

Hi list,

I know this has been a topic on this and other lists before but I couldn't find a solution to my problem. I'lve already contacted 3ware support and I'm waiting for an answer from their site (but maybe someone comes up with a quick solution here).

My setup:

Hardware: Xeon Quad Core, Intel Mainboard, 2GB RAM, 3ware 9560SE PCI-Express, 4x 1TB WD Disks, RAID-10 Array

Software: Ubuntu Hardy LTS, Kernel 2.6.26

When I create an ext3 FS directly on the RAID array (/dev/sda1) I get write speeds at ~95MB/sec and read speeds at ~390MB/sec. But when I add LVM into the mix, write speed drops down to 39MB/sec (all tested with dd + /dev/zero or /dev/null). After some research I found out that this might be related to bad performance of the 3ware driver with non-4K blocksizes:

blockdev --getbsz /dev/sda1
4096

blockdev --getbsz /dev/sda3
512

sda1 is formatted with ext3, sda3 acts as the physical volume for LVM. Is there any way to change the blocksize of an LVM PV or does anyone know if theres a way to tweak the 3ware driver to handle 512-Byte blocksizes better than it does now?

Mit freundlichen Grüßen / with kind regards

Rudolph Bott
-- 
Megabit Informationstechnik GmbH
Karstr.25  41068 Moenchengladbach  Tel:02161/30898-0  Fax:-18
AG MG HRB 10141, GF: Dipl.-Ing. Thomas Tillig, Michael Benten 

           reply	other threads:[~2008-12-17 15:27 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <8251455.241229524675229.JavaMail.rudi@toronto>]

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=26617199.341229527604820.JavaMail.rudi@toronto \
    --to=rb@megabit.net \
    --cc=linux-lvm@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.