From: "Swâmi Petaramesh" <swami@petaramesh.org>
To: linux-btrfs <linux-btrfs@vger.kernel.org>
Cc: "Fajar A. Nugraha" <list@fajar.net>
Subject: Re: Rename BTRfs to MuchSlowerFS ?
Date: Wed, 07 Sep 2011 16:15:19 +0200 [thread overview]
Message-ID: <1411501.d4mgBNBG2i@tethys> (raw)
In-Reply-To: <CAG1y0sd=fYDT4Z4J=HqYXSsuZGjyMbUgpbLiguqdnibwt9qqOw@mail.gmail.com>
Le Mercredi 7 Septembre 2011 00:11:25 vous avez =E9crit :
> Reading your post, at this point I'd actually recommend you stick wit=
h
> ext4.
I actually shifted back from BTRFS to ext4 and fell like having offered=
myself=20
a brand new computer, about 20 times faster, me happy ;-)
> Both btrfs and zfs are great, but IMHO btrfs is not ready for
> daily use by "ordinary" user yet, while zfs is a memory hog
> (especially for laptops, which is part of the reason why I'm using
> btrfs instead of zfs on this one).
True, ZFS is excellent but a memory hog (and strongly advises using a 6=
4-bit=20
OS) but I was surprised to discover that BTRFS was such a memory eater =
itself,=20
with kernel 3.0. My system was swapping like mad !
I use (kernel) ZFS on my 64-bit main machine and I'm plain happy with i=
t, and=20
tried ZFS on my 32-bit laptop in the hope to get more performance for l=
ess=20
memory ; alas I just got a memory-hungry system running damn slow... Fo=
r the=20
time being I will stick to ZFS for 64-bit machines with >=3D 4GB RAM, a=
nd to=20
ext4 for 32-bit systems with less RAM...
I don't feel that BTRFS gives any advantage in its current state of=20
development. Alas.
--=20
Sw=E2mi Petaramesh <swami@petaramesh.org> http://petaramesh.org PGP 907=
6E32E
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-09-07 14:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 13:51 Rename BTRfs to MuchSlowerFS ? Swâmi Petaramesh
2011-09-05 14:00 ` Hugo Mills
2011-09-05 14:20 ` Roman Mamedov
2011-09-05 17:10 ` Elric Milon
2011-09-05 14:17 ` David McBride
2011-09-05 19:25 ` Sergei Trofimovich
2011-09-06 15:30 ` Swâmi Petaramesh
2011-09-06 17:11 ` Fajar A. Nugraha
2011-09-07 14:15 ` Swâmi Petaramesh [this message]
2011-09-15 19:37 ` Felix Blanke
2011-09-15 22:16 ` Fajar A. Nugraha
2011-09-16 6:21 ` Maciej Marcin Piechotka
2011-09-16 6:42 ` Fajar A. Nugraha
2011-09-16 8:39 ` Maciej Marcin Piechotka
-- strict thread matches above, loose matches on Subject: below --
2011-09-05 16:23 Tomasz Chmielewski
2011-09-05 16:25 ` Christoph Hellwig
2011-09-05 16:29 ` Hugo Mills
2011-09-08 7:04 ` youagree
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=1411501.d4mgBNBG2i@tethys \
--to=swami@petaramesh.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=list@fajar.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).