From: Russell Coker <russell@coker.com.au>
To: Martin <m_btrfs@ml1.co.uk>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs filesystem freezing during snapshots
Date: Tue, 27 May 2014 02:19:47 +1000 [thread overview]
Message-ID: <1597628.qMVRAlqGPk@xev> (raw)
In-Reply-To: <llvm4o$9uv$1@ger.gmane.org>
On Mon, 26 May 2014 16:20:55 Martin wrote:
> That looks to be running on top of drbd which will add a network write
> overhead (unless you are dangerously running asynchronously!). Hence you
> will see IO speed related limits a little sooner...
http://etbe.coker.com.au/2012/01/05/drbd-benchmarking/
Last time I did DRBD performance testing I found that the synchronous option
was FASTER. My theory is that no-one does much work on the options that
aren't recommended.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2014-05-26 16:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 12:28 Btrfs filesystem freezing during snapshots David Bloquel
2014-05-26 15:20 ` Martin
2014-05-26 16:19 ` Russell Coker [this message]
2014-05-26 15:39 ` Duncan
2014-05-26 16:39 ` Roman Mamedov
2014-05-26 17:02 ` Roman Mamedov
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=1597628.qMVRAlqGPk@xev \
--to=russell@coker.com.au \
--cc=linux-btrfs@vger.kernel.org \
--cc=m_btrfs@ml1.co.uk \
/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).