All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sean Oh" <oh@storageone.co.kr>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] syncing with snapshots takes forever?
Date: Sat Jan 25 08:34:01 2003	[thread overview]
Message-ID: <002301c2c47e$b54fbb60$3200a8c0@COMPAQ> (raw)
In-Reply-To: 20030124111515.O12662@schatzie.adilger.int

----- Original Message -----
From: "Andreas Dilger" <adilger@clusterfs.com>
To: <linux-lvm@sistina.com>
Sent: Saturday, January 25, 2003 3:15 AM
Subject: Re: [linux-lvm] syncing with snapshots takes forever?

> The problem is that when you type "sync" you are actually writing (most
of)
> your file to disk 4 times - once for the initial LV (which was mostly
still
> in RAM I'm guessing), and once for each snapshot.

I understand that it is writing from memory to disk 4 times.(Yes, the data
is kept in memery until kernel dumps to disk, since the application I am
using does _async_ operation)

> Since you now have 4x
> the write load and it is not streaming, but random I/O it causes your
disks
> to thrash badly.  Add to that the fact that you are writing to a RAID
which
> needs to seek _every_ disk for each write, and you are in really bad
shape.


I do not think the RAID is one of the significant factor for the slowdown
here, since systems without RAID have the pretty much same problem.

> I'm guessing that if you put each snapshot on its own physical disk (maybe
> only keeping the original LV on the RAID device) you will see a lot of
> improvement.

I did.. see below

> Also, it would be interesting to know what the real performance
> of even the single 1GB write is (i.e. write + sync) because I'm guessing
> most of the data is still in memory.

Well, I have tested on the different system than my orignal posting. This
system has 4GB of RAM  and FC external RAID5 system, composing 4 RAID5
volumes with 5 FC disks each.

By doing 'sync ; time dd if=/dev/zero of=1G bs=1024k count=1000 ; time sync'
.

The dd write + sync speed on LV without snapshots was about110MB/s.
The dd write + sync speed on LV with 1 snapshots was about 5MB/s,too
The dd write + sync speed on LV with 2 snapshots was about 3.5MB/s,too
The dd write + sync speed on LV with 3 snapshots was about 3.2MB/s.

After putting the snapshot PVs on the different RAID volume:
The dd write + sync speed on LV with 1 snapshots was about 12MB/s,too
The dd write + sync speed on LV with 2 snapshots was about 9MB/s,too
The dd write + sync speed on LV with 2 snapshots was about 7MB/s,too

When I test with NFS(async mode) and SAMBA,they go fast until let's say a
few hundreds of MB is filled up in the memory, needed to be flushed and then
the trasfer suffers, nearly _STOPPED_ responding, producing 0 to a few
hundred _bytes_ for the transfer speed.

 > At, say, 50MB/s to disk you are still
> talking 3 or 4 minutes to write out 1GB, so even an ideal LV snapshot case
> would take 9-15 minutes to write out 4GB.


> Cheers, Andreas

Well, even with 1 snapshot, the throughput goes down to 1/10.

For my purpose, I would like to have NFS and SAMBA to transfer data
consistently with async mode. It seems to me that some logic in lvm snapshot
or kernel is causing those apps to stoped for a few tens of minutes when
memory is full and synced.
Do you know any patches to kernel or lvm that does not block(?) the I/O
operations while syncing or do something smarter for handling above issues?

      parent reply	other threads:[~2003-01-25  8:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-24  7:08 [linux-lvm] syncing with snapshots takes forever? Sean Oh
2003-01-24  7:33 ` Jan-Benedict Glaw
2003-01-24  7:56   ` Sean Oh
2003-01-24 12:16 ` Andreas Dilger
2003-01-24 12:27   ` Joe Thornber
2003-01-25  1:57     ` Sean Oh
2003-01-25  8:34   ` Sean Oh [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='002301c2c47e$b54fbb60$3200a8c0@COMPAQ' \
    --to=oh@storageone.co.kr \
    --cc=linux-lvm@sistina.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.