June 20, 2013

Post: MySQL 5.5 and MySQL 5.6 default variable values differences

… | | QUERY_CACHE_SIZE | 0 | 1048576 | | SLOW_QUERY_LOG_FILE | …could have been made even larger. Write intensive workload will do a lot better on MySQL…cache_size though would be larger by default…table=1 for most of workloads for years now. The exceptions have been when you have large number of tables

Post: Troubleshooting MySQL Memory Usage

MySQL 3.23 when there would only handful of places where memory could be allocated but it is a lot larger problems with MySQLfor Table Cache Related Allocations There are cases when MySQL will allocate a lot of memory for table cache, especially if you’re using large… valgrind are too slow to run in …

Post: MySQL extensions for hosting

being used at all and could be candidates for dropping. All the patch features will surely be a great help formysql> SHOW TABLE_STATISTICS LIKE ‘hosting2%’; +——————————–+———–+————–+————————-+ | Table

Post: Long PRIMARY KEY for Innodb tables

…checking/repairing large MyISAM tables in case of MySQL/System crash is painful and great to be avoided. Long …table scan for this table would also be slow as it is quite fragmented. Table however is not getting any table… ? In this case we could have multiple thumbnail sizes for the same image which …

Post: ORDER BY ... LIMIT Performance Optimization

…the table so indexes could be used on each of the tables to optimize order by, or at least local sort could be used for each … up in slow query log as query which does not use indexes, even if it is quite fast: mysql> explain … write another article about ORDER BY without limit and large tables soon.

Post: Join Optimizations in MySQL 5.6 and MariaDB 5.5

… you could be reading the same page multiple times. Consider if you have a small buffer pool and a very large number of rows from table2 that do not fit into the buffer pool, then worst case you could be reading… is slow as compared to MySQL 5.6. Next interesting thing are the last two columns of the table above and the values for

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

large log file generated. Another thing that we normally do is set the variable log_slowMySQL server, you would see an entry like this in the slowtables are probably being created because of blob columns being accessed by the query. So a quick fix here could be

Post: MySQL Server Memory Usage

be crashing , failing to execute queries or make operation to swap seriously slowing down. On now legacy 32bit platforms you couldbe large if you have a lot of tables. It also means user having CREATE TABLE privilege should be able to run MySQL

Post: New SpecJAppServer results at MySQL and Sun.

could be which makes it better to disable them. The MySQL Settings are probably what is the most interesting: MySQLtable_size=200M log-output = FILE log-slow-queries=/tmp/mysql-slow.log long_query_time = 1 innodb_data_home_dir = /data/mysql

Post: Announcing Percona Server for MySQL version 5.5.29-30.0

… of Percona Server for MySQL version 5.5.29… DROP TABLE performance were not adjusted for XtraDB. This could cause …and AIO routines if large innodb_log_block_…being logged even if they weren’t enabled for the slow query log. Bug fixed #730173 (Laurynas Biveinis). Fixed the incorrect help text for slow