All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Carlos R. Mafra" <crmafra-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
Cc: linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Re: NILFS2 on an Intel X25-M SSD
Date: Thu, 31 Dec 2009 10:47:18 +0100	[thread overview]
Message-ID: <4B3C7326.4010002@gmail.com> (raw)
In-Reply-To: <20091231.034629.85391956.ryusuke-sG5X7nlA6pw@public.gmane.org>

Am 30.12.2009 19:46, schrieb Ryusuke Konishi:
> On Tue, 29 Dec 2009 20:48:47 +0100, "Carlos R. Mafra" wrote:
>> Is there any specific tweak in NILFS2 to use with an SSD? Would you
>> reccomend using NILFS2 on a SSD right now?
>>
>> Is the issue mentioned here
>>
>> https://www.nilfs.org/pipermail/users/2009-March/000514.html
>>
>> about excessive writing in the GC already fixed?
>> That is the most pressing fear I have about NILFS2 for the SSD.
> 
> Not yet, sorry.  I'm working on some performance optimization for high
> speed drives espacially for SSD.  Revising GC is another priority, but
> it would need some time.
> 
> The massive I/O by the current garbage collector may shorten the life
> of SSD.  So, I don't recommend yet.

Hmm, then I won't use NILFS2 on the SSD for now.

I am testing it in an external HD for the last two days to get a feeling,
and so far everything looks good and stable. It is a pity that the 
massive I/O problem kind of prevents putting it on the SSD.

Naively I would think that the GC will always create some I/O that
other filesystems don't have, by its very definition. Can you
quantify by how much the current GC is writing in excess and what would
be the acceptable numbers?

> If you are not interested in snapshots, I think nilfs is not always a
> good choice because high-end SSD drives are already doing lfs like
> optimization internally.  Intel SSD exactly looks like this sort of
> drives though I'm using nilfs on X25-M and X25-E ;)

The log-structured nature of the file system seemed a good thing for
the health of the SSD, yes. But the snapshot feature is something
interesting to have too and I was willing to have it :-)

  parent reply	other threads:[~2009-12-31  9:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4B3A5D1F.9010002@gmail.com>
     [not found] ` <4B3A5D1F.9010002-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-12-30 18:46   ` NILFS2 on an Intel X25-M SSD Ryusuke Konishi
     [not found]     ` <20091231.034629.85391956.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-12-31  9:47       ` Carlos R. Mafra [this message]
     [not found]         ` <4B3C7326.4010002-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-01-02 17:24           ` Ryusuke Konishi
     [not found]             ` <20100103.022425.52166650.ryusuke-sG5X7nlA6pw@public.gmane.org>
2010-01-02 20:44               ` Carlos R. Mafra
     [not found]                 ` <20100102204417.GA6877-8NNKxJcwqxqHjx4iBuKRcg@public.gmane.org>
2010-01-03 12:39                   ` Ryusuke Konishi
2010-01-02 20:00 admin-/LHdS3kC8BfYtjvyW6yDsg

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=4B3C7326.4010002@gmail.com \
    --to=crmafra-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-nilfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=ryusuke-sG5X7nlA6pw@public.gmane.org \
    --cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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.