From: Stefan Hajnoczi <stefanha@gmail.com>
To: Dietmar Maurer <dietmar@proxmox.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v4 3/6] add backup related monitor commands
Date: Mon, 4 Mar 2013 13:58:06 +0100 [thread overview]
Message-ID: <20130304125806.GA18476@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <24E144B8C0207547AD09C467A8259F7557B12DDC@lisa.maurer-it.com>
On Thu, Feb 28, 2013 at 03:24:27PM +0000, Dietmar Maurer wrote:
> > > Unfortunately, NBD add considerable overheads. I guess the socket
> > communications copies data.
> > > This is really unnecessary if I can write directly to the output stream.
> >
> > The disk is the bottleneck, not memory bandwidth. Hard disks only do
> > 10-100 MB/sec and SSDs only do a couple 100 MB/sec. Memory copy is
> > insignificant compared to the I/O activity required to copy out the entire disk
> > image, not to mention delaying guest writes until we read the original data from
> > the disk.
> >
> > Unless there's a concrete performance problem here this is premature
> > optimization.
>
> I currently test with about 700MB read speed, and get a slow down by factor 1.7.
> So memory copy is very significant , or there is something wrong with nbd.c.
What are the details of the test?
Is it using 64 KB writes and have you tried 256 KB writes?
Stefan
next parent reply other threads:[~2013-03-04 12:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130220142939.GF16633@stefanha-thinkpad.muc.redhat.com>
[not found] ` <24E144B8C0207547AD09C467A8259F7557A6EFE2@lisa.maurer-it.com>
[not found] ` <20130221130345.GD22957@stefanha-thinkpad.redhat.com>
[not found] ` <24E144B8C0207547AD09C467A8259F7557A6FAAC@lisa.maurer-it.com>
[not found] ` <20130222095736.GA6107@stefanha-thinkpad.redhat.com>
[not found] ` <24E144B8C0207547AD09C467A8259F7557A70A61@lisa.maurer-it.com>
[not found] ` <20130225134551.GE3202@stefanha-thinkpad.redhat.com>
[not found] ` <24E144B8C0207547AD09C467A8259F7557AE0931@lisa.maurer-it.com>
[not found] ` <20130228144920.GD18389@stefanha-thinkpad.redhat.com>
[not found] ` <24E144B8C0207547AD09C467A8259F7557B12DDC@lisa.maurer-it.com>
2013-03-04 12:58 ` Stefan Hajnoczi [this message]
2013-03-04 13:16 ` [Qemu-devel] [PATCH v4 3/6] add backup related monitor commands Dietmar Maurer
2013-03-04 13:55 ` Kevin Wolf
2013-03-04 14:33 ` Dietmar Maurer
2013-03-06 12:44 ` Stefan Hajnoczi
2013-03-06 14:42 ` Dietmar Maurer
2013-03-06 15:22 ` Kevin Wolf
2013-03-06 15:33 ` Dietmar Maurer
2013-03-06 15:48 ` Kevin Wolf
2013-03-06 17:39 ` Dietmar Maurer
2013-03-07 9:04 ` Kevin Wolf
2013-03-07 9:22 ` Dietmar Maurer
2013-03-07 9:05 ` Stefan Hajnoczi
2013-03-07 9:28 ` Dietmar Maurer
2013-03-08 10:48 ` Stefan Hajnoczi
2013-03-08 11:01 ` Dietmar Maurer
2013-03-08 16:29 ` Stefan Hajnoczi
2013-03-08 17:44 ` Dietmar Maurer
2013-03-10 6:43 ` Stefan Hajnoczi
2013-03-10 9:32 ` Dietmar Maurer
2013-03-10 11:11 ` Stefan Hajnoczi
2013-03-09 14:13 ` Dietmar Maurer
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=20130304125806.GA18476@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=dietmar@proxmox.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).