From: Sander <sander@humilis.net>
To: "Swâmi Petaramesh" <swami@petaramesh.org>
Cc: Jan Schmidt <list.btrfs@jan-o-sch.net>, linux-btrfs@vger.kernel.org
Subject: Re: Example of BTRFS uglyssima performance : Bitcoin
Date: Tue, 4 Dec 2012 09:57:09 +0100 [thread overview]
Message-ID: <20121204085709.GA18531@panda> (raw)
In-Reply-To: <50BCDA36.1050900@petaramesh.org>
Swâmi Petaramesh wrote (ao):
> 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...)
If your system is stable, you could also consider running bitcoin with
eatmydata.
Sander
next prev parent reply other threads:[~2012-12-04 8:57 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
2012-12-04 8:57 ` Sander [this message]
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=20121204085709.GA18531@panda \
--to=sander@humilis.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=list.btrfs@jan-o-sch.net \
--cc=swami@petaramesh.org \
/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.