… enabled. MyISAM in PXC May Lead to Inconsistencies and May Not Even Work! MyISAM tables are supported within Percona XtraDB Cluster, however, MyISAM has… anyone who wants to, but still have MyISAM tables. You can still try by filtering MyISAM tables though if you can leave them behind… any workload – it shines with small transactions but not with big ones. If you are consistently running overnight reporting jobs and…
Post: Follow these basics when migrating to Percona XtraDB Cluster for MySQL
May 1, 2013 By 10 Comments
Post: Recovering Innodb table Corruption
July 4, 2008 By 22 Comments
… all your data in MyISAM table so all you have to do is to drop old table and convert new table back to Innodb… using MyISAM table for the reason you’ll see later. You may think why do not you simply rebuild table by using OPTIMIZE TABLE… we get about 50 rows per page so not a big surprise 30 rows was not enough – typically if page directory…
Post: Why MySQL could be slow with large tables ?
June 9, 2006 By 141 Comments
… fully sequential access, jam packed rows – quite possible scenario for MyISAM tables. Now if we take the same hard drive for fully… in sorted order can be a lot of help for big scans. This will reduce the gap but I doubt it… data you’re going to work with in temporary table etc. Prefer full table scans to index accesses – For large data sets…
Post: High-Performance Click Analysis with MySQL
December 22, 2008 By 13 Comments
…” and is it stored in a VARCHAR(36)? When tables get big, every byte matters a lot. Use the smallest… of repairing huge MyISAM tables and taking downtime, I would not use MyISAM for anything but read-only tables when things get big. And… row-based replication in a way. When you’re updating big aggregate tables, don’t work with giant chunks of them at…
Post: Should you move from MyISAM to Innodb ?
January 12, 2009 By 59 Comments
… dealing with very large number of tables, slow data load and ALTER TABLE and others. Another big one is COUNT(*) without where clause…) and when use other tables when it really gives substantial gains. I would not switch table to MyISAM because it gives 5% performance improvement but I can perfectly use MyISAM (or Archive) for logging…
Post: InnoDB vs MyISAM vs Falcon benchmarks - part 1
January 8, 2007 By 117 Comments
…=1500M –max-connections=1500 –table-cache=512 –net_read_timeout=30 –net_write_timeout=30 –backlog=128 MyISAM / InnoDB: libexec/mysqld –no… LIMIT queries will be fixed before release. MyISAM shows stable result. InnoDB is better than MyISAM by 58% in case with 4… way to handle multi-versioning. I think this is a big weakness of Falcon, as ‘using index’ is very common optimization…
Post: Why you should ignore MySQL's key cache hit ratio
February 28, 2010 By 28 Comments
… a machine that’s dedicated to MyISAM tables. Consider your mixture of storage engines (some InnoDB, some MyISAM, which is more important to you, etc) and choose an amount of memory based on how important those tables are to you, how big the indexes are on disk, and so on…
Post: The MySQL optimizer, the OS cache, and sequential versus random I/O
April 28, 2008 By 17 Comments
… take a look at the tables. mysql> show table status like ‘fact’\G *************************** 1. row *************************** Name: fact Engine: MyISAM Rows: 147045493 Avg_row…: dim2 Engine: MyISAM Rows: 811 Avg_row_length: 105 Data_length: 85368 Index_length: 154624 It’s a big fact table and two…
Post: MySQL Upgrade Webinar Questions Followup
June 28, 2012 By 7 Comments
… continues to support MyISAM tables, so you can continue use them as needed. I would evaluate changing though as MyISAM tables are on track to be depreciated in future MySQL versions also MyISAM tables are essentially at the… for the worst during Upgrade? This is one of the big challenges with upgrade which can’t be resolved in all…
Post: MySQL File System Fragmentation Benchmarks
March 21, 2008 By 28 Comments
… specified amount of tables and does specified number of inserts going to random tables. I used default MySQL settings for MyISAM (table_cache=64… though table_cache was just 64. I expect this is because updating index header (most complex part of opening and closing MyISAM table) can happen by OS in background and flushing 1000 pages each 30 seconds is not big overhead for…
