Comments on: Profiling MySQL Memory Usage With Valgrind Massif https://www.percona.com/blog/profiling-mysql-memory-usage-with-valgrind-massif/ Wed, 07 Aug 2019 13:18:43 +0000 hourly 1 https://wordpress.org/?v=6.5.2 By: Laurynas Biveinis https://www.percona.com/blog/profiling-mysql-memory-usage-with-valgrind-massif/#comment-1805676 Wed, 05 Jun 2013 14:59:05 +0000 https://www.percona.com/blog/?p=12155#comment-1805676 Aurimas –

You-don’t-run-that-in-production, the slowdown is 10x or more. If you have a server that needs Valgrinding, first you have to reduce the workload to the lightest possible that still exhibits the issue you are investigating.

]]> By: Aurimas Mikalauskas https://www.percona.com/blog/profiling-mysql-memory-usage-with-valgrind-massif/#comment-1804915 Wed, 05 Jun 2013 10:25:12 +0000 https://www.percona.com/blog/?p=12155#comment-1804915 Hi Roel, –

thanks so much for this very useful post. I was wondering – what is the performance penalty of running mysqld (or any other program) under Massif/Valgrind ? It is probably going to vary a lot, but I wonder if it’s like barely noticeable or is it more like you-don’t-run-that-in-production ?

]]> By: Mark Callaghan https://www.percona.com/blog/profiling-mysql-memory-usage-with-valgrind-massif/#comment-1206118 Thu, 10 Jan 2013 15:55:44 +0000 https://www.percona.com/blog/?p=12155#comment-1206118 Another conclusion — it would be nice if this feature request open since 2007 with an example implementation as fixed in official MySQL — http://bugs.mysql.com/bug.php?id=31932. It is fun when something is open long enough that I file duplicate feature requests — http://bugs.mysql.com/bug.php?id=64353

]]>