June 19, 2013

Post: Should you move from MyISAM to Innodb ?

in the end for most users – you do not get to deal with recovering tables on the crash or partially executed statements. Table locks is noMyISAM kills Innodb, such as copying binary tables between the servers. It is important the team understands Innodb and knows how toin the MySQL server – in

Post: Using LVM for MySQL Backup and Replication Setup

MyISAMto do atomic snapshot of many volumes. Lets speak a bit about how LVM and snapshotting into do to perform backup of MySQL Database (or create slave) using LVM2 on Linux. 1) Connect to MySQL and run FLUSH TABLES WITH READ LOCK

Post: Hacking to make ALTER TABLE online for certain changes

to remove auto_increment from 100G table. No matter if it’s InnoDB or MyISAM, you’d usually ALTER TABLE `huge_tabletables with read lock, (3) swap .frm files while keeping mysql suspended and (4) unlock the tables afterwards: — 1. mysql> CREATE TABLE `huge_table

Post: Innodb Performance Optimization Basics

in MySQL 4.1 and now stable enough to use. Also check if your application can run inin locking in 5.0 and even more to come with MySQLno OS changes and have no changes done to application which was written keeping MyISAM tables in

Post: Performance problem with Innodb and DROP TABLE

… is done while table_cache lock is being held so no other queries…the list you really need to think how large it can get…use innodb_file_per_table=0 for such tables (thankfully you can change this variable online in Innodb Plugin, MySQL…depending on buffer pool size. MyISAM tables creating/dropping was…

Post: MySQL Slow query log in the table

MySQL slow query log logged in mysql.slow_log table instead of the file as you had in previous versions. We rarely would useusing LIKE statement. As default table format for slow_log is CSV with no indexes typical operations like finding how many queries were accumulated intable to MyISAM

Post: MySQL optimizer: ANALYZE TABLE and Waiting for table flush

MySQL has detected that the underlying table has changed and it needs to close and reopen it using FLUSH. Therefore the table will be lockedto finish than the original query. On the other hand, if the table is MyISAM there will be no

Comment: Beware of MyISAM Key Cache mutex contention

used for fulltext search, so no InnoDB possible for now. My question is, is it possible that it is only related to a MySQLlocked on a resource is it possible that the scheduler of a modern operating system wastes 90% time into substitute the fulltext search on MyISAM table

Post: Paul McCullagh answers your questions about PBXT

how does it compare in performance?  When would I use PBXT instead of a storage engine like MyISAMMySQL calls the engine “init” method on startup it is holding the global LOCK_plugin lock. In init, the engine needs to do recovery. In

Post: Falcon Storage Engine Design Review

TABLE STATUS” is not showing index sized in the release we tested it is hard to see how small indexes really are. [-] Nousingin MySQL anyway though). Very interesting to see how this one will compare to