linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Luigi Semenzato <semenzato@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: extremely long blockages when doing random writes to SSD
Date: Fri, 26 Jun 2015 09:58:08 +0900	[thread overview]
Message-ID: <20150626005808.GA5704@swordfish> (raw)
In-Reply-To: <CAA25o9ShiKyPTBYbVooA=azb+XO9PWFtididoyPa4s-v56mvBg@mail.gmail.com>

Hello,

On (06/25/15 11:24), Luigi Semenzato wrote:
> I looked at this some more and I am not sure that there is any bug, or
> other possible tuning.
> 
> While the random-write process runs, iostat -x -k 1 reports these numbers:
> 
> average queue size: around 300
> average write wait: typically 200 to 400 ms, but can be over 1000 ms
> average read wait: typically 50 to 100 ms
> 
> (more info at crbug.com/414709)
> 
> The read latency may be enough to explain the jank.  In addition, the
> browser can do fsyncs, and I think that those will block for a long
> time.
> 
> Ionice doesn't seem to make a difference.  I suspect that once the
> blocks are in the output queue, it's first-come/first-serve.  Is this
> correct or am I confused?
> 
> We can fix this on the application side but only partially.  The OS
> version updater can use O_SYNC.  The problem is that his can happen in
> a number of situations, such as when simply downloading a large file,
> and in other code we don't control.
> 

do you use CONFIG_IOSCHED_DEADLINE or CONFIG_IOSCHED_CFQ?

	-ss

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2015-06-26  0:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-24 21:54 extremely long blockages when doing random writes to SSD Luigi Semenzato
2015-06-24 22:25 ` Andrew Morton
2015-06-24 23:43   ` Luigi Semenzato
2015-06-25 18:24     ` Luigi Semenzato
2015-06-26  0:58       ` Sergey Senozhatsky [this message]
2015-06-26  1:31         ` Luigi Semenzato
2015-06-26  1:42           ` Sergey Senozhatsky
2015-06-26  1:43             ` Luigi Semenzato
2015-06-26 18:24               ` Luigi Semenzato

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=20150626005808.GA5704@swordfish \
    --to=sergey.senozhatsky.work@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=semenzato@google.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;
as well as URLs for NNTP newsgroup(s).