public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Clark <sclark46@earthlink.net>
To: Theodore Tso <tytso@MIT.EDU>
Cc: Vincent Pelletier <plr.vincent@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: ext4 bug ? "Intel 320 SSD write performance – contd."
Date: Tue, 01 Nov 2011 10:00:46 -0400	[thread overview]
Message-ID: <4EAFFB8E.20605@earthlink.net> (raw)
In-Reply-To: <C838F22F-D7B1-4911-B6F6-214240A77859@mit.edu>

On 11/01/2011 09:41 AM, Theodore Tso wrote:
> On Nov 1, 2011, at 9:34 AM, Stephen Clark wrote:
>
>    
>>> You can enable the trim behaviour by default by adding to your
>>> /etc/mke2fs.conf file:
>>>
>>> [defaults]
>>> 	discard = true
>>>
>>> But then it's on your head if anything bad happens.  :-/
>>>
>>>          	      	      	      - Ted
>>>
>>>
>>>        
>> <snip>
>>
>> What about using discard in fstab like:
>> LABEL=/ /                      ext4    defaults,discard,noatime,nodiratime        1 1
>>      
> That does something different; this does continuous discards as you delete files.   This is probably the best thing to do if you are using thin-provisioning.   However, with SATA devices, a discard requires a queue flush, which can be a performance disaster.   (Also some cheaper SSD's also have real performance difficulties if there are frequent trims.)   There have also been reports that high frequency discards can trigger bugs that cause crappier SSD's to turn themselves into bricks.   The performance problems and the possibility of bricking crappier SSD's is why this isn't turned on by default.
>
> Because of this, another method is to do FITRIM's periodically using cron.   This has less of a performance impact, so it's probably the better approach in many cases.
>
> Basically, with SSD's and thin-provisioning systems, we are very much at the mercy at the competence of firmware authors.   As we know, sometimes firmware authors can be quite competent, or very, extremely incompetent.   So there will be a wide range of outcomes, which is one of the reasons why the best answer is to test to see what works best for you, preferably before you put use your systems in production.
>
> -- Ted
>    
So what I hear if that if you are using sata interface and not doing 
virtualization we should be using FITRIMS's from  a cron job. At what 
frequency should
we be doing this?

Thanks,
Steve

-- 

"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety."  (Ben Franklin)

"The course of history shows that as a government grows, liberty
decreases."  (Thomas Jefferson)




  reply	other threads:[~2011-11-01 14:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-31 20:38 ext4 bug ? "Intel 320 SSD write performance – contd." Vincent Pelletier
2011-10-31 21:09 ` Ted Ts'o
2011-10-31 21:47   ` Vincent Pelletier
2011-11-01 13:34   ` Stephen Clark
2011-11-01 13:41     ` Theodore Tso
2011-11-01 14:00       ` Stephen Clark [this message]
2012-01-15 18:37   ` ext4 bug ? "Intel 320 SSD write performance ??? contd." Pavel Machek

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=4EAFFB8E.20605@earthlink.net \
    --to=sclark46@earthlink.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=plr.vincent@gmail.com \
    --cc=tytso@MIT.EDU \
    /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