From: Larry Dickson <ldickson@cuttedge.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Quick Question RE Snapshots
Date: Tue, 27 Oct 2009 08:32:59 -0800 [thread overview]
Message-ID: <1c748a490910270932i4358d850va6d3a232775950dc@mail.gmail.com> (raw)
In-Reply-To: <4AE711B2.1060800@worldspice.net>
[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]
In my experience yes - if you are doing long sequential writes, snapshot
turns them into random IO. If you were doing short random writes to begin
with, then snapshot should not have such a huge relative effect, because the
non-snapshot performance is already slow.
Larry Dickson
Cutting Edge Networked Storage
On 10/27/09, Ryan Anderson <ryan@worldspice.net> wrote:
> I'm sure this has been covered before, but I didn't see it in the
> archive: Is a near 90% drop in write performance "normal" snapshot
> behavior? If so, :(
>
> If not, are there any good resources I should be looking at? Every
> search I perform comes up with one of two types of articles on the matter:
>
>
> 1) Snapshots are awesome! They let you...(list of really nifty things)
>
> 2) Snapshots suck! My system is completely useless while they're active!
>
> --
> Ryan Anderson
> (901) 843 9300
> Systems Engineer
> WorldSpice Technologies
>
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
>
[-- Attachment #2: Type: text/html, Size: 1661 bytes --]
prev parent reply other threads:[~2009-10-27 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 15:28 [linux-lvm] Quick Question RE Snapshots Ryan Anderson
2009-10-27 16:32 ` Larry Dickson [this message]
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=1c748a490910270932i4358d850va6d3a232775950dc@mail.gmail.com \
--to=ldickson@cuttedge.com \
--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).