All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <martin@lichtvoll.de>
To: Dewangga <dewanggaba@xtremenitro.org>
Cc: xfs@oss.sgi.com
Subject: Re: Valid Benchmark Value & Methods
Date: Thu, 07 May 2015 15:54:06 +0200	[thread overview]
Message-ID: <1889263.HCPQcpsWke@merkaba> (raw)
In-Reply-To: <554B5782.4040303@xtremenitro.org>

Am Donnerstag, 7. Mai 2015, 19:16:02 schrieb Dewangga:
> Hello Martin,
> Thanks for your reply, yes I've read that link, but another question,
> is noatime,nodiratime,etc still valid for performance tuning guidance?
> Even the default mount options only "rw,inode64,seclabel,attr2".
> 
> Is it still increase the performance if the additional mount options
> added?

noatime implies nodiratime as far as I know.

And yes, it can help for databases for example. I think official 
recommendation for MySQL and PostgreSQL is to use noatime. There is a post 
by Theodore T´so somewhere about make clean workload on Ext4 with noatime, 
relatime and strictatime handling and only noatime considerably reduced the 
amount of writes.

noatime is a generic tuning option which can help with other filesystems as 
well.

-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2015-05-07 13:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-07 11:24 Valid Benchmark Value & Methods Dewangga
2015-05-07 11:48 ` Martin Steigerwald
2015-05-07 11:49 ` Martin Steigerwald
2015-05-07 12:16   ` Dewangga
2015-05-07 13:54     ` Martin Steigerwald [this message]
2015-05-07 22:55     ` Dave Chinner
2015-05-08  5:53       ` Dewangga Bachrul Alam

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=1889263.HCPQcpsWke@merkaba \
    --to=martin@lichtvoll.de \
    --cc=dewanggaba@xtremenitro.org \
    --cc=xfs@oss.sgi.com \
    /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.