All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"nefelim4ag@gmail.com" <nefelim4ag@gmail.com>
Subject: Re: LIO: FILEIO vs IBLOCK read performance
Date: Wed, 1 Feb 2017 19:55:21 +0000	[thread overview]
Message-ID: <1485978900.2560.9.camel@sandisk.com> (raw)
In-Reply-To: <CAGqmi770AJ1v5188DijUB6oNZvsrRAMca4yeo=mqe1AW_x-Zjw@mail.gmail.com>

On Wed, 2017-02-01 at 11:18 +0300, Timofey Titovets wrote:
> so, short results (random read on /dev/sdb on client):
> block + /dev/sdb ~ 500 iops (emulate_write_cache=0)
> fileio + /dev/sdb ~ 90 iops (emulate_write_cache=0)
> fileio + /dev/sdb ~ 90 iops (emulate_write_cache=1)
> fileio + /storage/LUN/1 ~90 iops (emulate_write_cache=0)
> fileio + /storage/LUN/1 ~90 iops (emulate_write_cache=1)
> block + /dev/loop0 ~ 90 iops loop directio=0
> block + /dev/loop0 ~ 500 iops loop directio=0

The address of the LIO mailing list is target-devel@vger.kernel.org instead
of linux-scsi@vger.kernel.org. Anyway, have you tried to disable readahead
on /dev/sdb (blockdev --setra / --setfra)? Readahead can have a significant
negative impact on random I/O. There is a heuristic in the kernel for
automatically disabling readahead for random I/O but maybe that algorithm
did not recognize your workload properly.

Bart.

      reply	other threads:[~2017-02-01 19:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-01  8:18 LIO: FILEIO vs IBLOCK read performance Timofey Titovets
2017-02-01 19:55 ` Bart Van Assche [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=1485978900.2560.9.camel@sandisk.com \
    --to=bart.vanassche@sandisk.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nefelim4ag@gmail.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.