June 20, 2013

Post: MySQL Query Patterns, Optimized - Webinar questions followup

how easy it is?  ;-)  Generative grammars like SQL can produce an infinite variety of  queries.  The query optimizer analyzes queries for common patterns the MySQLquery that took half the time. An important conclusion of my presentation today is that sometimes you find unexpected differences in

Post: 5 Percona Toolkit Tools for MySQL That Could Save Your Day: April 3 Webinar

MySQL. In this presentation, you will learn how you can use some of these tools to solve typical, real-world MySQL database administration challenges, such as: Selecting which queries you should try to optimize to get better response times How

Post: How to find MySQL queries worth optimizing ?

I often get is how one can find out queries which should be optimized. By looking at pt-queryI get the following record in the slow query log: # Time: 120911 17:18:05 # User@Host: root[root] @ localhost [] # Thread_id: 65005 Schema: sbtest Last

Post: How to Identify Bad Queries in MySQL

last three-part definition is where I can‘t be sure that I‘ve got a complete definition. Now, given the definition above, howin MySQL for years. This is necessary for determining whether a group of queries completed in a cluster. One-second granularity (what you get in standard MySQL

Post: How to recover deleted rows from an InnoDB Tablespace

How can I recover deleted rows? We’re going to follow the same example as inin our hands the last step is to import it in our database: mysqlQuery OK, 3 rows affected (0.01 sec) Records: 3 Deleted: 0 Skipped: 0 Warnings: 0 mysql

Post: Flexviews - part 3 - improving query performance using materialized views

time. Both of these views build in about the same about of time: mysql> call flexviews.enable( -> flexviews.get_id(‘demo’,'complete_example2′)); QueryI hope this helps you understand how Flexviews can help you ensure fast response times in

Post: InnoDB Full-text Search in MySQL 5.6 (part 1)

I think that hope may be premature. While it is true that InnoDB full-text search in MySQL 5.6 (part 1) in MySQLI ran OPTIMIZE TABLE several more times, and each execution took between 6 and 8 seconds, but the output of the query against I

Post: Identifying the load with the help of pt-query-digest and Percona Server

in MySQL. This is very helpful for measurement as otherwise we might not catch some long running connections. Now let’s getquery was executed. Next the “Query_time distribution” section shows how this query times mostly, which you can see majority of the time lies in

Post: Modeling MySQL Capacity by Measuring Resource Consumptions

Last errno 0 # Users user # Query_time distribution # 1us # 10us # # 100us ################################################################ # 1ms ############# # 10ms ###### # 100ms # # 1s # 10s+ We can see this query takes 2ms to respond in