by Peter Zaitsev | Sep 3, 2008 | Insight for DBAs
Following up on my Previous Post I decided to do little test to see how accurate stats we can get for for Index Stats created by ANALYZE TABLE for MyISAM and Innodb. But before we go into that I wanted to highlight about using ANALYZE TABLE in production as some...
by Peter Zaitsev | Sep 2, 2008 | Insight for DBAs
As you might know ANALYZE TABLE just quickly updates table statistics using index dives, unlike with MyISAM when it scans indexes holding table lock for long period of time. So ANALYZE TABLE should be very fast and non intrusive operation doing just little update on...
by Vadim Tkachenko | Jul 31, 2008 | Percona Software
We prepared RPMs of our release for RedHat 5 / CentOS 5 x86_64 platform. https://www.percona.com/blog/mysql/RPM/RHEL5/5.0.62/ There was question what patcheset includes and if there is manuals. We have: microsecond resolution in slow-log extended query plan in...
by Peter Zaitsev | Jul 4, 2008 | Insight for DBAs
Assume you’re running MySQL with Innodb tables and you’ve got crappy hardware, driver bug, kernel bug, unlucky power failure or some rare MySQL bug and some pages in Innodb tablespace got corrupted. In such cases Innodb will typically print something like...
by Baron Schwartz | Jul 3, 2008 | Benchmarks, Insight for Developers
Recently I had a customer ask me about loading two huge files into InnoDB with LOAD DATA INFILE. The goal was to load this data on many servers without putting it into the binary log. While this is generally a fast way to load data (especially if you disable unique...
by Baron Schwartz | May 24, 2008 | Insight for DBAs
Much has been written about the new InnoDB pluggable storage engine, which Innobase released at the MySQL conference last month. We’ve written posts ourselves about its fast index creation capabilities and the compressed row format, and how that affects...
by Peter Zaitsev | May 1, 2008 | Insight for DBAs
In the previous post I mentioned a way I use to preload Clustered Index (data) for Innodb tables. Though I thought this topic would benefit from a bit more information. But lest first start with feature request for Innodb Team: All ways I mention here are hacks and...
by Peter Zaitsev | May 1, 2008 | Insight for DBAs
Recently I was working with the customer who need quick warmup – to get Innodb table fetched in memory as fast as possible to get good in memory access performance. To do it I run the query: “SELECT count(*) FROM tbl WHERE non_idx_col=0” I use this...
by Peter Zaitsev | Apr 26, 2008 | Hardware and Storage
Let us talk few more about disks. You might have read my previous post and Matt’s Reply and it looks like there are few more things to clarify and explain. Before I get to main topic of the article lets comment on IO vs Disk question. If you look at Disk Based...
by Peter Zaitsev | Apr 23, 2008 | Insight for Developers
Sometimes you have the task of storing multiple of boolean values (yes/now or something similar) in the table and if you get many columns and many rows you may want to store them as efficient way as possible. For MyISAM tables you could use BIT(1) fields which get...
by Alexey Kovyrin | Apr 23, 2008 | Benchmarks, Insight for DBAs
In one of his recent posts Vadim already gave some information about possible benefits from using new InnoDB file format but in this post I’d like to share some real-life example how compression in InnoDB plugin could be useful for large warehousing tasks. One...
by Vadim Tkachenko | Apr 23, 2008 | Insight for DBAs
New features of InnoDB – compression format and fast index creation sound so promising so I spent some time to research time and sizes on data we have on our production. The schema of one of shards is CREATE TABLE `article87` ( `id` bigint(20) unsigned NOT NULL,...
by Vadim Tkachenko | Apr 20, 2008 | Insight for DBAs
It seems there is interesting problem with compatibility of MySQL binaries and binaries of third-party plugins. I personally found and there is confirmation from InnoDB team that current InnoDB-plugin binaries do not work with lastest 5.1.24-rc binaries. It was very...
by Vadim Tkachenko | Apr 15, 2008 | Insight for DBAs
Looking into InnoDB docs I found list of names of future InnoDB file formats: Antelope, Barracuda, Cheetah, Dragon, Elk, Fox, Gazelle, Hornet, Impala, Jaguar, Kangaroo, Leopard, Moose, Nautilus, Ocelot, Porpoise, Quail, Rabbit, Shark, Tiger, Urchin, Viper, Whale, X, Y...
by Peter Zaitsev | Apr 15, 2008 | Uncategorized
As you probably have already heard Innodb Announced new Plugin version for MySQL 5.1 So now you can see Heikki and the Team were not just doing only bug fixes for last two years, but rather kept very quite. We had access to this code for few weeks and should say we...
by Peter Zaitsev | Apr 8, 2008 | Insight for DBAs
If you’re using Innodb tables MySQL has innodb_flush_log_at_trx_commit variable which defines how durable your transactions are. If you have high durability requirements you set it to 1 and log records are pushed directly to the disk on transaction commit. If...
by Peter Zaitsev | Mar 31, 2008 | Benchmarks
Recently I have had a chance to check out MySQL Performance on “Memory Appliance” by Violin Memory which can be used as extremely high speed storage system. I helped Violin Memory to optimize MySQL for customer workload and Violin memory and also had a...
by Peter Zaitsev | Mar 21, 2008 | Benchmarks
Few days ago I wrote about testing writing to many files and seeing how this affects sequential read performance. I was very interested to see how it shows itself with real tables so I’ve got the script and ran tests for MyISAM and Innodb tables on ext3...
by Peter Zaitsev | Jan 29, 2008 | Insight for DBAs
As MySQL Manual Says Query Cache works with transactions with Innodb tables but it does not tell you how and with which restrictions. According to my tests it works but it is very restricted and one could expect it to work much better: The result set can be retrieved...
by Peter Zaitsev | Jan 29, 2008 | Insight for DBAs
As you might know even if you’re only using Innodb tables your replication is not completely crash safe – if Slave MySQL Server crashes/power goes down it is likely for relay logs to run out of sync (they are not synced to the disk) plus position on the...
