public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: Re: noop or deadline on an SSD?
Date: Sun, 21 Apr 2013 19:58:00 -0500	[thread overview]
Message-ID: <51748B18.6040309@hardwarefreak.com> (raw)
In-Reply-To: <CAEDdjHcoZc2eS=hgb7K7BVf=2z28uh3CMuEU8+qFPp5UFvj-iQ@mail.gmail.com>

On 4/21/2013 5:38 PM, Pedro Ribeiro wrote:

> Ok, I also read that with an SSD I should be using noop or deadline. And
> which one of these would perform better with XFS with an SSD? And while I'm
> at it, which one would be best for a  mechanical drive?

$ echo [noop|deadline] > /sys/block/sdX/queue/scheduler

Given the ease with which one can switch between the two, it's far
better to test each yourself with your hardware and workloads, than to
rely on any generic advice.

-- 
Stan

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

      reply	other threads:[~2013-04-22  0:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-21 22:38 noop or deadline on an SSD? Pedro Ribeiro
2013-04-22  0:58 ` Stan Hoeppner [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=51748B18.6040309@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox