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: Fri, 17 Oct 2014 16:29:29 +0000 [thread overview]
Message-ID: <bug-86471-13602-AW4uRZDgkk@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 #2 from Markus Königshaus <m.koenigshaus@wut.de> ---
Hi Theodore,
even after a very long wait, the performance remain so low. The performance is
also low when you copy files. I have used dd, so I create only reproducible
write access.
I have now tested the ext3 FS, same result.
After some debugging I found out, there is a delay in start_this_handle (look
at the timing), with echo 5 > /sys/kernel/debug/jbd/jbd-debug I get:
>> before mysqlshutdown:
...
[ 40.400755] fs/jbd/transaction.c: (journal_stop, 1380): h_ref 2 -> 1
[ 40.400755]
[ 40.400765] fs/jbd/transaction.c: (journal_stop, 1384): Handle df03e000
going down
[ 40.400765]
[ 40.400789] fs/jbd/transaction.c: (journal_start, 290): from journal_start
[ 40.400789]
[ 40.400801] fs/jbd/transaction.c: (start_this_handle, 110): New handle
df03e000 going live.
[ 40.400801]
[ 40.400813] fs/jbd/transaction.c: (start_this_handle, 229): Handle df03e000
given 14 credits (total 21, free 14286)
...
>> after mysqlshutdown:
...
[ 61.383886] fs/jbd/transaction.c: (journal_stop, 1380): h_ref 2 -> 1
[ 61.383886]
[ 61.383896] fs/jbd/transaction.c: (journal_stop, 1384): Handle df03e000
going down
[ 61.383896]
[ 61.393528] fs/jbd/transaction.c: (start_this_handle, 110): New handle
df03e000 going live.
[ 61.393528]
[ 61.393541] fs/jbd/transaction.c: (start_this_handle, 229): Handle df03e000
given 14 credits (total 21, free 14271)
...
I try to isolate the problem in more detail next week, I would welcome tips and
help for my try.
Regards, Markus
--
You are receiving this mail because:
You are watching the assignee of the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-10-17 16:29 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 [this message]
2014-10-22 16:00 ` bugzilla-daemon
2014-10-22 20:22 ` bugzilla-daemon
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-AW4uRZDgkk@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 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).