public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Big I/O latencies, except when iotop is hooked
Date: Wed, 9 May 2012 20:43:11 +0000	[thread overview]
Message-ID: <201205092043.11544.arnd@arndb.de> (raw)
In-Reply-To: <CAMP44s2eKgTzn9q1CN1X-8P+m0bcTw+UCz7FGQ1ekjzRe8j0SQ@mail.gmail.com>

On Wednesday 09 May 2012, Felipe Contreras wrote:
> And it doesn't tell me why I see the issue on my SSD as well; albeit
> with much less delay.
> 
> I'll try what you suggest, maybe I will get better performance by
> aligning the partitions, but the real issue seems to lie elsewhere,
> right?

For anything but the absolute worst devices, misaligning the partition
should cause a linear increase in latency (maybe factor 2 in the worst
case), so it doesn't explain the entire thing. However, you can use
flashbench to find out the erase block size. If it's larger than 4MB,
you definitely have a problem even with ext4 or btrfs. The latencies
you get from garbage collection for a single write are roughly the time
it takes to write one erase block, and that can be up to a second in the
worst case (slow media with large erase blocks).

	Arnd

  reply	other threads:[~2012-05-09 20:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09 16:20 Big I/O latencies, except when iotop is hooked Felipe Contreras
2012-05-09 17:56 ` Arnd Bergmann
2012-05-09 20:16   ` Felipe Contreras
2012-05-09 20:43     ` Arnd Bergmann [this message]
2012-05-09 22:19   ` Felipe Contreras
2012-05-10 10:49     ` Arnd Bergmann
2012-05-14  8:59       ` Arnd Bergmann
2012-05-14  9:08         ` Felipe Contreras
2012-05-10  8:24   ` Felipe Contreras

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=201205092043.11544.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=felipe.contreras@gmail.com \
    --cc=linux-kernel@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