All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 86471] drastic reduction of write performance after the termination of mysqld
Date: Wed, 22 Oct 2014 20:22:55 +0000	[thread overview]
Message-ID: <bug-86471-13602-rB1bknwNLA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-86471-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=86471

--- Comment #4 from Theodore Tso <tytso@mit.edu> ---
Are you sure this is actually a problem?    Could it just be that when mysqld
shuts down, it's issuing a huge number of buffered writes which is just taking
a long, long time to get written out to your eMMC device (which is typically
very, *very* slow to handle writes).

I had suggested using blktrace to see if I/O is going on.   You could also try
looking using iostat or the dstat program.   If it's just that I/O is still
happening, then things may be working normally --- just that eMMC might be a
bad match with a high performance database workload.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2014-10-22 20:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-17 13:14 [Bug 86471] New: drastic reduction of write performance after the termination of mysqld bugzilla-daemon
2014-10-17 16:10 ` [Bug 86471] " bugzilla-daemon
2014-10-17 16:29 ` bugzilla-daemon
2014-10-22 16:00 ` bugzilla-daemon
2014-10-22 20:22 ` bugzilla-daemon [this message]
2014-10-23 10:34 ` bugzilla-daemon
2014-10-23 16:36 ` bugzilla-daemon
2014-10-24 15:14 ` bugzilla-daemon
2014-10-24 15:34 ` bugzilla-daemon
2014-11-13 14:24 ` bugzilla-daemon
2014-11-13 14:33 ` bugzilla-daemon
2014-11-13 14:41 ` bugzilla-daemon

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=bug-86471-13602-rB1bknwNLA@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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 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.