Emergency

Search Results for: max row size in innodb table

DROP TABLE and stalls: Lazy Drop Table in Percona Server and the new fixes in MySQL

Suppose you have turned on innodb_file_per_table (which means that each table has its own tablespace), and you have to drop tables in a background every hour or every day. If its once every day then …

Read More
 

Benchmarking single-row insert performance on Amazon EC2

I have been working for a customer benchmarking insert performance on Amazon EC2, and I have some interesting results that I wanted to share. I used a nice and effective tool iiBench which has been …

Read More
 

Evidenzia Upgrades to TokuDB v5.2 to Address Storage Growth and Scale Performance

by:

Ensuring sufficient disk I/O to catch copyright violations at network speed. Evidenzia GmbH & Co. KG Issues addressed: Storage growth, including maxed-out disk I/O utilization Performance issues and business impact due to slow selects Inability to revise …

Read More
 

Review of Virident FlashMAX MLC cards

I have been following Virident for a long time (e.g. https://www.percona.com/blog/2010/06/15/virident-tachion-new-player-on-flash-pci-e-cards-market/). They have great PCIe Flash cards based on SLC NAND. I always thought that Virident needed to come up with an MLC card, and …

Read More
 

Improved InnoDB fast index creation

One of the serious limitations in the fast index creation feature introduced in the InnoDB plugin is that it only works when indexes are explicitly created using ALTER TABLE or CREATE INDEX. Peter has already …

Read More
 

Online Advertiser Intent Media Selects TokuDB over InnoDB and NoSQL for Big Data Ad-Hoc Analysis

by:

Intent Media Issue addressed: Ad hoc analytics on clickstream data arriving too fast for InnoDB or NoSQL to handle. TokuDB powers an online advertising application The Company: Headquartered in New York, Intent Media is a …

Read More
 

InnoDB compression woes

InnoDB compression is getting some traction, and I see quite contradictory opinions. Someone has successful deployments in productions, and someone says that compression in current implementation is useless. To get some initial impression about performance …

Read More
 

Innodb row size limitation

I recently worked on a customer case where at seemingly random times, inserts would fail with Innodb error 139. This is a rather simple problem, but due to it’s nature, it may only affect you …

Read More
 

Innodb undo segment size and transaction isolation

You might know if you have long running transactions you’re risking having a lot of “garbage” accumulated in undo segment size which can cause performance degradation as well as increased disk space usage. Long transactions …

Read More
 

Reasons for run-away main Innodb Tablespace

So you’re running MySQL With innodb_file_per_table option but your ibdata1 file which holds main (or system) tablespace have grown dramatically from its starting 10MB size. What could be the reason of this growth and what …

Read More