All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: Malinka Rellikwodahs <aelmalinka@gmail.com>
Cc: Mark van Walraven <markv@netvalue.net.nz>,
	kvm@vger.kernel.org, nikola.ciprich@linuxbox.cz
Subject: Re: kvm-83 write performance raw
Date: Tue, 3 Mar 2009 16:13:25 +0100	[thread overview]
Message-ID: <20090303151324.GA7090@develbox.linuxbox.cz> (raw)
In-Reply-To: <aa2a0fc0903021300o5934521fi8c571850939d27ce@mail.gmail.com>

Hi,
I think DRBD *MIGHT* be Your problem anyways...
Can You try repeating Your measurments with
no-disk-barrier, no-disk-flushes, no-disk-drain
options for Your drbd devices and report the results?
nik

On Mon, Mar 02, 2009 at 04:00:57PM -0500, Malinka Rellikwodahs wrote:
> On Mon, Mar 2, 2009 at 15:53, Mark van Walraven <markv@netvalue.net.nz> wrote:
> > On Mon, Mar 02, 2009 at 03:11:59PM -0500, Malinka Rellikwodahs wrote:
> >> when running with a raw disk image as a file or a raw disk image on an
> >> lvm vg, I'm getting very low performance on write (5-10 MB/s) however
> >> when using qcow2 format disk image the write speed is much better
> >> (~30MB/s), which is consistant with a very similar setup running
> >> kvm-68.  Unfortunately when running the test with qcow2 the system
> >> becomes unresponsive for a brief time during the test.
> >
> >> The host is running raid5 and drbd (drive replication software),
> >> however performance on the host is performaning well and avoiding the
> >> drbd layer in the guest does not improve performance, but running on
> >> qcow2 does.
> >>
> >> Any thoughts/suggestions of what could be wrong or what to do to fix this?
> >
> > RAID1 has *much* better write performance.  With striping RAIDs, alignment
> > is important.  RAID controllers sometimes introduce hidden alignment
> > offsets.  Excessive read-ahead is a waste of time with a lot of small
> > random I/O, which is what I see mostly with guests on flat disk images.
> >
> > With LVM, it pays to make sure the LVs are aligned to the disk.  I prefer
> > boundaries with multiples of at least 64-sectors, which makes the LVM
> > overhead virtually disappear.  I align the guest filesystems too, when
> > I can.
> >
> > I don't think DRBD has an effect on alignment, but you might look at
> > keeping the metadata on another drive.
> >
> > Block - rather than file - images are much faster.
> >
> > Hope this helps,
> 
> It does, however unless I'm missing something the performance is being
> lost not in the lvm/raid/drbd config, because I'm using the same setup
> for other partitions which are used for data on the host and write
> performance to those drives is just fine.
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

-- 
-------------------------------------
Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava

tel.:   +420 596 603 142
fax:    +420 596 621 273
mobil:  +420 777 093 799
www.linuxbox.cz

mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------

  reply	other threads:[~2009-03-03 15:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02 20:11 kvm-83 write performance raw Malinka Rellikwodahs
2009-03-02 20:35 ` Anthony Liguori
2009-03-02 20:37   ` Malinka Rellikwodahs
2009-03-02 20:39     ` Malinka Rellikwodahs
2009-03-02 21:22       ` Anthony Liguori
2009-03-02 21:39         ` Malinka Rellikwodahs
2009-03-02 22:21           ` Anthony Liguori
2009-03-09 15:09           ` Avi Kivity
2009-03-02 20:53 ` Mark van Walraven
2009-03-02 21:00   ` Malinka Rellikwodahs
2009-03-03 15:13     ` Nikola Ciprich [this message]
     [not found]       ` <aa2a0fc0903051110q528da32ek17b0f6468d0f15ff@mail.gmail.com>
2009-03-05 19:11         ` Fwd: " Malinka Rellikwodahs
2009-03-06  0:14           ` Malinka Rellikwodahs
2009-03-09 15:40           ` Fwd: " Nikola Ciprich
2009-03-04 22:28   ` Paolo Pedaletti
2009-03-05  2:09     ` Mark van Walraven

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=20090303151324.GA7090@develbox.linuxbox.cz \
    --to=extmaillist@linuxbox.cz \
    --cc=aelmalinka@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=markv@netvalue.net.nz \
    --cc=nikola.ciprich@linuxbox.cz \
    /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.