From: Jan Kara <jack@suse.cz>
To: "HUANG Weller (CM/ESW12-CN)" <Weller.Huang@cn.bosch.com>
Cc: Jan Kara <jack@suse.cz>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: which IO-scheduler is best for flash based storage device with ext4
Date: Wed, 13 Jan 2016 10:06:08 +0100 [thread overview]
Message-ID: <20160113090608.GB14630@quack.suse.cz> (raw)
In-Reply-To: <a6b26fd61d88475784c7745b92fe0ae2@SGPMBX1004.APAC.bosch.com>
Hi,
On Wed 13-01-16 06:33:28, HUANG Weller (CM/ESW12-CN) wrote:
> Could you tell me which IO-scheduler is best for flash based storage
> device with ext4 ? Just search from WWW, I saw it is said that the noop
> is best because the CFQ is design for the mechanical hard disk. And I
> did the performance test with IOzone between the IO-scheduler noop and
> cfq. The performance difference is small. So here I want to get some
> answer from you about this question.
Yes, CFQ is meant for classical rotational disk. For normal SSDs I use
deadline IO scheduler (it does more request merging, prefers read over
writes), for high-end I'd use noop.
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2016-01-13 9:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 6:33 which IO-scheduler is best for flash based storage device with ext4 HUANG Weller (CM/ESW12-CN)
2016-01-13 9:06 ` Jan Kara [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=20160113090608.GB14630@quack.suse.cz \
--to=jack@suse.cz \
--cc=Weller.Huang@cn.bosch.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).