Comments on: Performance Optimization and Six Sigma http://www.mysqlperformanceblog.com/2010/06/07/performance-optimization-and-six-sigma/ Percona's MySQL & InnoDB performance and scalability blog Sat, 11 Feb 2012 16:45:54 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Baron Schwartz http://www.mysqlperformanceblog.com/2010/06/07/performance-optimization-and-six-sigma/comment-page-1/#comment-766295 Baron Schwartz Tue, 08 Jun 2010 14:08:27 +0000 http://www.mysqlperformanceblog.com/?p=2958#comment-766295 My thoughts on this are here: http://code.google.com/p/maatkit/issues/detail?id=1054 My thoughts on this are here: http://code.google.com/p/maatkit/issues/detail?id=1054

]]> By: Baron Schwartz http://www.mysqlperformanceblog.com/2010/06/07/performance-optimization-and-six-sigma/comment-page-1/#comment-766293 Baron Schwartz Tue, 08 Jun 2010 14:03:59 +0000 http://www.mysqlperformanceblog.com/?p=2958#comment-766293 Peter, the acceptable query time for Apdex would have to be a command-line option. I recognize that it's different for various classes of queries, of course. Peter, the acceptable query time for Apdex would have to be a command-line option. I recognize that it’s different for various classes of queries, of course.

]]> By: Calvin http://www.mysqlperformanceblog.com/2010/06/07/performance-optimization-and-six-sigma/comment-page-1/#comment-766287 Calvin Tue, 08 Jun 2010 10:30:22 +0000 http://www.mysqlperformanceblog.com/?p=2958#comment-766287 or in other words there is less than 3 defects per million. Some amendment need to be done for the above sentence, it will be better to make it less than 3.4 defect per million since if there are 3.1 defect found, it still consider as 6 sigma or in other words there is less than 3 defects per million.

Some amendment need to be done for the above sentence, it will be better to make it less than 3.4 defect per million since if there are 3.1 defect found, it still consider as 6 sigma

]]> By: Arjen Lentz http://www.mysqlperformanceblog.com/2010/06/07/performance-optimization-and-six-sigma/comment-page-1/#comment-766271 Arjen Lentz Tue, 08 Jun 2010 04:33:55 +0000 http://www.mysqlperformanceblog.com/?p=2958#comment-766271 From our experience, many companies first need to deal with uptime resilience - of course, when building that, the desired performance stability can and should be considered. From our experience, many companies first need to deal with uptime resilience – of course, when building that, the desired performance stability can and should be considered.

]]> By: peter http://www.mysqlperformanceblog.com/2010/06/07/performance-optimization-and-six-sigma/comment-page-1/#comment-766265 peter Tue, 08 Jun 2010 02:52:29 +0000 http://www.mysqlperformanceblog.com/?p=2958#comment-766265 Baron, Yes... and I asked for just 95 because this is what was used in TPC-C, SpecJAppServer and similar benchmarks. Now I think we need a higher percentile number. Re Apdex how do you know acceptable query execution time ? Baron,

Yes… and I asked for just 95 because this is what was used in TPC-C, SpecJAppServer and similar benchmarks. Now I think we need a higher percentile number. Re Apdex how do you know acceptable query execution time ?

]]> By: Baron Schwartz http://www.mysqlperformanceblog.com/2010/06/07/performance-optimization-and-six-sigma/comment-page-1/#comment-766261 Baron Schwartz Tue, 08 Jun 2010 02:24:18 +0000 http://www.mysqlperformanceblog.com/?p=2958#comment-766261 We used 95% in mk-query-digest because that's what you asked for :-D But I agree -- a much tighter restriction is needed for looking at long periods of time. I've actually been thinking a lot about including Apdex scores in mk-query-digest. Time to go add a feature request to the bug tracker, while it's on my mind. We used 95% in mk-query-digest because that’s what you asked for :-D But I agree — a much tighter restriction is needed for looking at long periods of time. I’ve actually been thinking a lot about including Apdex scores in mk-query-digest. Time to go add a feature request to the bug tracker, while it’s on my mind.

]]>