May 24, 2012

Post: Joining many tables in MySQL - optimizer_search_depth

in case) which would take 5 seconds even though in the read less than 1000 rows and doing it completely in memory. Thedo we have value of 62 being default in MySQL 5.5 which can produce very expensive plan selections ? Investigating this further I found the

Post: Index Condition Pushdown in MySQL 5.6 and MariaDB 5.5 and its performance impact

I have been working with Peter in preparation for the talk comparing the optimizer enhancements in MySQL 5.6 and MariaDB 5.5. We are taking a look at and benchmarking optimizer enhancements one by one. So in the same way this blog post is aimed at a new optimizer enhancement Index Condition Pushdown (ICP). Its available in both MySQL 5…

Post: InnoDB's gap locks

the record 25 is locked. Then, we try to insert another value on the second session: transaction2 > START TRANSACTION; transaction2 > INSERT INTO t VALUESthe statement, the behavior of these locks can be different. In the following link there is a good source of information: http://dev.mysql

Post: How Percona strives to remain neutral and independent

the prominent companies in the MySQL…Percona values. How do we balance the …not something I‘ve …the solution without any interaction with the vendor, if that is not necessary to give you the best service. In summary, you get thethe issues we identified. Sometimes the outcome is more positive the second

Post: How to Monitor MySQL with Percona's Nagios Plugins

…monitor in MySQL. Those …value. This plugin, perhaps more than any other, should only be used judiciously. The server has been restarted recently. It is surprising howget the incremental increase in a variable such as Queries and alert on a queries-per-second threshold. (I don’t suggest doing this; I

Post: How Percona does a MySQL Performance Audit

The first iteration is the current values since the server was booted; the second and subsequent are incremental differences. II‘m examining the status values for Created_tmp_tables and Created_disk_tmp_tables, I‘ll paste in mysql

Post: Modeling MySQL Capacity by Measuring Resource Consumptions

How to get CPU consumption per query ? You can take a look at procfs for MySQL process: root@ubuntu:/var/log/mysqlThe #14 and #15 here is kernel and user CPU usage of MySQL process in 1/100 of the second… can get the value from User Statistics …second ? I will need to do another 280 reads per second

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

mysql> call flexviews.refresh( -> flexviews.get_id(‘demo’, -> ‘dashboard_customer_sales’),’BOTH’,NULL); Query OK, 0 rows affected (7.01 sec) The second

Post: What to tune in MySQL Server after installation

in MySQL Server straight after installation, assuming it was installed with default settings. I‘m surprised howin MySQL Servers only few of them are really important for most common workload. After you getthe disk each second so you normally would not loose more than 1-2 sec worth of updates. Value

Post: MySQL 5.5.8 - in search of stability

in the second we are limited by the capacity of REDO logs. So, what do we getI received with MySQL 5.5.8 (with innodb_doublewrite enabled). In summary, my conclusion is: You can try to get stable throughput in MySQL