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 16:00:51 +0000 [thread overview]
Message-ID: <bug-86471-13602-lurJZXY6BS@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 #3 from Markus Königshaus <m.koenigshaus@wut.de> ---
It looks like a problem in the writeback - mechanism, not ext4 related, sorry:
cd /sys/kernel/debug/tracing/
echo function > current_tracer
echo writeback* > set_ftrace_filter
>> before mysqlshutdown
# tracer: function
#
# entries-in-buffer/entries-written: 3/3 #P:1
#
# _-----=> irqs-off
# / _----=> need-resched
# | / _---=> hardirq/softirq
# || / _--=> preempt-depth
# ||| / delay
# TASK-PID CPU# |||| TIMESTAMP FUNCTION
# | | | |||| | |
dd-3666 [000] ...1 1338.484467: writeback_in_progress
<-balance_dirty_pages_ratelimited
kworker/u2:2-1001 [000] ...2 1338.557118: writeback_sb_inodes
<-__writeback_inodes_wb
kworker/u2:2-1001 [000] ...2 1338.557160: writeback_sb_inodes
<-__writeback_inodes_wb
>> after mysqlshutdown:
# tracer: function
#
# entries-in-buffer/entries-written: 384/384 #P:1
#
# _-----=> irqs-off
# / _----=> need-resched
# | / _---=> hardirq/softirq
# || / _--=> preempt-depth
# ||| / delay
# TASK-PID CPU# |||| TIMESTAMP FUNCTION
# | | | |||| | |
dd-3733 [000] ...1 1403.061232: writeback_in_progress
<-balance_dirty_pages_ratelimited
kworker/u2:2-1001 [000] ...2 1403.061277: writeback_sb_inodes
<-__writeback_inodes_wb
dd-3733 [000] ...1 1403.071042: writeback_in_progress
<-balance_dirty_pages_ratelimited
dd-3733 [000] ...1 1403.071328: writeback_in_progress
<-balance_dirty_pages_ratelimited
kworker/u2:2-1001 [000] ...2 1403.071350: writeback_sb_inodes
<-__writeback_inodes_wb
dd-3733 [000] ...1 1403.077546: writeback_in_progress
<-balance_dirty_pages_ratelimited
[ ... repeat 368 times ... ]
dd-3733 [000] ...1 1404.327043: writeback_in_progress
<-balance_dirty_pages_ratelimited
dd-3733 [000] ...1 1404.327306: writeback_in_progress
<-balance_dirty_pages_ratelimited
kworker/u2:2-1001 [000] ...2 1404.327336: writeback_sb_inodes
<-__writeback_inodes_wb
dd-3733 [000] ...1 1404.337125: writeback_in_progress
<-balance_dirty_pages_ratelimited
someone an idea, where to report this problem?
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-22 16:00 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 [this message]
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-lurJZXY6BS@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.