From: Ross Vandegrift <ross@kallisti.us>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Poor LVM dump performance
Date: Tue, 23 Jan 2007 22:33:52 -0500 [thread overview]
Message-ID: <20070124033351.GA11234@kallisti.us> (raw)
Hi everyone,
I've run into som substantial read degredation when using dump or tar
to backup filesystems that are stored on LVM2 LVs. Many times in the
past I have seen dump run at speeds approaching block device speeds;
50-60MiB/s, similar with tar.
I'm seeing speeds in the range of 3-4MiB/s when dumping a filesystem.
If I increase dump's blocksize to 128KiB records, speed jumps up to
about 20KiB/s, which is better but still frustratingly slow. Going
to 1024KiB gets me about 28MiB/s.
Is this amount of performance loss expected? My LV is just two SATA
hard disks that I put into a VG. Stupid benchmarks with dd gives me a
raw read speed from the LV of about 60MiB/sec.
Any ideas on what's slowing down dump?
--
Ross Vandegrift
ross@kallisti.us
"The good Christian should beware of mathematicians, and all those who
make empty prophecies. The danger already exists that the mathematicians
have made a covenant with the devil to darken the spirit and to confine
man in the bonds of Hell."
--St. Augustine, De Genesi ad Litteram, Book II, xviii, 37
reply other threads:[~2007-01-24 3:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070124033351.GA11234@kallisti.us \
--to=ross@kallisti.us \
--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 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).