linux-ext4 - [Bug 86471] drastic reduction of write performance after the termination of mysqld

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 22 Oct 2014 20:22:55 +0000
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 86471] drastic reduction of write performance after the
 termination of mysqld

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

--- Comment #4 from Theodore Tso <tytso@....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.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html