Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Uncle Stoatwarbler <stoatwblr@gmail.com>
To: zfs-discuss@zfsonlinux.org, Roman Mamedov <rm@romanrm.ru>,
	"BTRFS, Linux" <linux-btrfs@vger.kernel.org>
Subject: Re: [zfs-discuss] Re: Moving...
Date: Wed, 03 Apr 2013 09:47:28 +0100	[thread overview]
Message-ID: <515BECA0.8020302@gmail.com> (raw)
In-Reply-To: <515B120F.6000004@petaramesh.org>

On 02/04/13 18:14, Swâmi Petaramesh wrote:

> My netbook (now ZFS) boots to GDM in less than 30 seconds. My son's same
> machine (except for the FS) takes 75 MORE seconds.

my (5 year old) laptop with a relatively slow SSD in it boots to GDM 
(Mint LXDE) in about 5 seconds with ext4. A 9 year old laptop fitted 
with a very slow PATA SSD takes about 9 seconds to do the same.

I'm not so sure that ZFS is a good fit for single drive machines ((Nor 
is ext4 for SSDs for that matter), but I'm happy to be corrected.

What I do know from banging hard on both is that I'd far sooner trust 
ZFS in an enterprise environment than BTRFS (or XFS), because I'm not 
really that happy about the idea of having to periodically restore 
500Tb+ of data from backups. Speed is a secondary issue, but ZFS is 
definitely faster at large scale.

There's a lot of wheel reinvention going on and I feel there must be 
some way of merging the good parts of both sets of code, then moving on.



  parent reply	other threads:[~2013-04-03  8:47 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 ` Moving Roman Mamedov
2013-04-02 17:14   ` Moving Swâmi Petaramesh
2013-04-02 17:19     ` Moving Harald Glatt
2013-04-03  8:47     ` Uncle Stoatwarbler [this message]
2013-04-03  9:14       ` [zfs-discuss] Moving 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=515BECA0.8020302@gmail.com \
    --to=stoatwblr@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rm@romanrm.ru \
    --cc=zfs-discuss@zfsonlinux.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