From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: Jan Schmidt <list.btrfs@jan-o-sch.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Example of BTRFS uglyssima performance : Bitcoin
Date: Mon, 03 Dec 2012 17:58:30 +0100 [thread overview]
Message-ID: <50BCDA36.1050900@petaramesh.org> (raw)
In-Reply-To: <50BCCB85.9010905@jan-o-sch.net>
Le 03/12/2012 16:55, Jan Schmidt a écrit :
> Use ubuntu (which in the default setup means you're using ecryptfs for
> your /home),
I actually do not use ecryptfs here, but OTOH I have BTRFS over LUKS/LVM.
But I've been using pretty *anything over LUKS/LVM for years, and I've
never notice it cause any (noticeable to the point of becoming annoying)
system slowdown, whatever tasks I may have processed in such setups
(including servers, big databases, compilations, NAS, etc...)
So I doubt that the encryption is involved here... At least not very
heavily involved. But I may ask my son if he volunteers to test the same
on his unencrypted BTRFS netbook...
> Besides that, as Hugo told you, you can disable btrfs cow on the database files,
> but given my experiences I wouldn't put too much hope into that part.
As far as I understood, this option won't work unless I have a 3.7+
kernel...
BTW, what is the effect of "nocow" with respect to snapshots ? I would
assume that then, snapshots contain the current data ?
Kind regards.
--
Swâmi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 9076E32E
Ne cherchez pas : Je ne suis pas sur Facebook.
next prev parent reply other threads:[~2012-12-03 16:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 11:54 Example of BTRFS uglyssima performance : Bitcoin Swâmi Petaramesh
2012-12-03 12:09 ` Hugo Mills
2012-12-03 12:24 ` Swâmi Petaramesh
2012-12-04 2:18 ` Chris Samuel
2012-12-04 7:22 ` Swâmi Petaramesh
2012-12-03 19:13 ` Wade Cline
2012-12-03 15:55 ` Jan Schmidt
2012-12-03 16:58 ` Swâmi Petaramesh [this message]
2012-12-04 8:57 ` Sander
2012-12-03 19:32 ` Gregory Maxwell
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=50BCDA36.1050900@petaramesh.org \
--to=swami@petaramesh.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=list.btrfs@jan-o-sch.net \
/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).