Hi, Never used it on production. From my point of view, it should be disabled by default, but included. The whole purpose of this variable is to have a way to analyze/optimize performances easily, when needed; if it's enable by default, we have a perf hit, so that's counterproductive. I assume it should be possible to work to remove the performance hit when disabled but included ? Thanks, Jocelyn Le 03/06/2014 10:20, Colin Charles a écrit :
Hi all,
Recently there was chat about how PERFORMANCE_SCHEMA was enabled by mistake and it should be disabled in the 10.0 series. I'm curious - how many of you are using PERFORMANCE_SCHEMA? Is it a problem to turn it on, if you use it?
I'm referring to: https://mariadb.atlassian.net/browse/MDEV-6249
Looking from the webscalesql list, there are examples of performance degradation: https://groups.google.com/d/msg/webscalesql/B-4bPIb8mHI/eUNsl0lSfbMJ https://groups.google.com/d/msg/webscalesql/B-4bPIb8mHI/-YZMMCuPw3QJ
quote: "Our perf testing agrees with your assessment (we see about a 5%-6% perf hit when it's included and on, and a 2%-3% hit when it's included but off)"
Please discuss this, either here or on MDEV-6249
Thanks
cheers, -colin
-- Colin Charles, Chief Evangelist, SkySQL - The MariaDB Company blog: http://bytebot.net/blog/| t: +6-012-204-3201 | Skype: colincharles
_______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : maria-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp