From: Roman Mamedov <rm@romanrm.ru>
To: "Swâmi Petaramesh" <swami@petaramesh.org>
Cc: "BTRFS, Linux" <linux-btrfs@vger.kernel.org>
Subject: Re: Moving...
Date: Tue, 2 Apr 2013 23:04:21 +0600 [thread overview]
Message-ID: <20130402230421.016afe58@natsu> (raw)
In-Reply-To: <515A95C7.5090607@petaramesh.org>
[-- Attachment #1: Type: text/plain, Size: 1555 bytes --]
On Tue, 02 Apr 2013 10:24:39 +0200
Swâmi Petaramesh <swami@petaramesh.org> wrote:
> Goodbye BTRFS, hello ZFS :-)
>
> I'm finally making the move, I couldn't stand the terrible BTRFS
> performance anymore, and spending 2 long minutes waiting for the HD LED
> to come off everytime I clicked anywhere.
>
> Did what I could, got the latest kernels, defragged, removed BTRFS
> snapshots, to no avail...
>
> So I'm in process of moving the 3 main laptops in here from BTRFS to ZFS...
Whatever works for you --
but at this point I trust my data to BTRFS more, than I would trust ZFS.
(of course having current backups etc).
The following may not sound like a compliment to BTRFS; but on my filesystems
with heavy snapshotting, recently I am trialling a practice to run major apps
like a mail client and a browser via "eatmydata", which overrides and NOOPs
fsync. Since in any case I have "sync; btrfs sub snap...." on those machines
set to every 30 minutes in crontab, the potential of data loss due to
"eatmydata" is never too great.
I noticed the general experience is a lot snappier this way. You could try at
least to verify whether or not your HD LED issues (:D) are indeed caused by
slow fsyncs, or by something else.
I should note that I currently use a 3.7 series kernel, and haven't upgraded
to 3.8 and 3.9 yet, AFAIK those had some fsync improvements which might render
this trick useless. But this still doesn't change the fact that apps in
general seem to over-use fsync.
--
With respect,
Roman
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-04-02 17:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 8:24 Moving Swâmi Petaramesh
2013-04-02 17:04 ` Roman Mamedov [this message]
2013-04-02 17:14 ` Moving Swâmi Petaramesh
2013-04-02 17:19 ` Moving Harald Glatt
2013-04-03 8:47 ` [zfs-discuss] Moving Uncle Stoatwarbler
2013-04-03 9:14 ` Swâmi Petaramesh
2013-04-03 16:55 ` Moving Goffredo Baroncelli
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=20130402230421.016afe58@natsu \
--to=rm@romanrm.ru \
--cc=linux-btrfs@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox