From: "norritt" <norritt@t-online.de>
To: linux-ext4@vger.kernel.org
Cc: norritt@t-online.de
Subject: Re: Ongoing data reorganization/defragmentation?
Date: Thu, 13 Sep 2012 14:54:27 +0200 [thread overview]
Message-ID: <5051D783.4000300@cube.nornet.local> (raw)
In-Reply-To: <alpine.LFD.2.00.1209121411410.2222@new-host-2>
On 12.09.2012 20:15, Lukáš Czerner wrote:
> On Wed, 12 Sep 2012, norritt@t-online.de wrote:
>
> From what I've found out it's a good idea to:
> - mount with noatime, discard (if drive supports trim)
> The -o discard option might be tricky since some devices still
> handles it quite badly and you can experience big performance drops
> (http://people.redhat.com/lczerner/discard/ although it is somewhat
> outdated already). But you might to try to see yourself if it does
> not hurt your performance.
>
> The other option would be to use batched discard with fstrim (see
> fstrim from util-linux) and run it once per (day, week, month).
>
> Thanks!
> -Lukas
>
Hi Lukáš,
thank you for pointing out the performance issue with the discard mount
option, I hadn't read about that yet. As far is I know I'm using a quite
special SSD (SanDisk, with a SanDisk controller), where most other SSDs
on the market seem to be based on Marvell, Sandforce or Indilinx
controllers. I saw that you were using SSDs from various vendors for
your benchmarking tests. Was a model with SanDisk controller among the
drives you tested? Would postmark data about disks with SanDisk
controller be of interest to you?
Regards Nor
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-09-13 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 16:36 Ongoing data reorganization/defragmentation? norritt
2012-09-12 17:35 ` Andreas Dilger
2012-09-13 12:20 ` norritt
2012-09-12 18:15 ` Lukáš Czerner
2012-09-13 12:54 ` norritt [this message]
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=5051D783.4000300@cube.nornet.local \
--to=norritt@t-online.de \
--cc=linux-ext4@vger.kernel.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.