You can now yum (RPM) or apt-get (DEB) MariaDB 5.1.39, courtesy of OurDelta and in close cooperation with Monty Program Ab. Simply follow the info on the CentOS, Debian or Ubuntu pages.
(note: give the mirrors some hours to sync up)
Quick overview
For the past two months, I have been running tests on TokuDB in my free time. TokuDB is a storage engine put out by Tokutek. TokuDB uses fractal tree indexes instead of B-tree indexes to improve performance, which is dramatically noticeable when dealing with large tables (over 100 million rows).
For those that like the information “above the fold”, here is a table with results from a test comparing InnoDB and TokuDB. All the steps are explained in the post below, if you want more details, but here’s the table:
| Action | InnoDB | TokuDB |
|---|---|---|
| Importing ~40 million rows | 119 min 20.596 sec | 69 min 1.982 sec |
| INSERTing again, ~80 million rows total | 5 hours 13 min 52.58 sec … |
One problem made me puzzled for couple hours, but it was really interesting to figure out what's going on.
So let me introduce problem at first. The table is
PLAIN TEXT CODE:
Table has 11864696 rows and takes Data_length: 698,351,616 bytes on disk
The problem is that after restoring table from mysqldump, the query that scans data by primary key was slow. How slow ? Let me show.
The query in …
[Read more]Someone recently posted this to an email list as a sample of an interesting SHOW INNODB STATUS output:
mysql> SHOW ENGINE INNODB STATUS\G
_______ _______
|\ /|( ____ \( ____ \
| ) ( || ( \/| ( \/
| | | || (_____ | (__
| | | |(_____ )| __)
| | | | ) || (
| (___) |/\____) || (____/\
(_______)\_______)(_______/
_______ _______ _______ _________ _______ _______ _______ _______
( ____ )( ___ )( ____ \\__ __/( ____ \( ____ )( ____ \( ____ \
| ( )|| ( ) || ( \/ ) ( | ( \/| ( )|| ( \/| ( \/
| (____)|| | | || (_____ | | | | | (____)|| (__ | (_____
| _____)| | | |(_____ ) | | | | ____ | __)| __) (_____ )
| ( | | | | ) | | | | | \_ )| (\ ( | ( ) |
| ) | (___) |/\____) | | | | (___) || ) \ \__| (____/\/\____) |
|/ (_______)\_______) )_( (_______)|/ \__/(_______/\_______) I thought it was worth …
[Read more]
A recent photo from Highload.ru
I said in my last post, that we're interested in speaking at MySQL meetups, and I'm happy to say that the Los Angeles MySQL Meetup has taken us up on the offer.
On November 18th, I'll be giving an introductory talk on InnoDB/XtraDB Performance Optimization. I will be the second speaker, with Carl Gelbart first speaking on Infobright.
What brings me to LA? On the same day (18th Nov) I'll be teaching a one day class on Performance Optimization for MySQL with InnoDB and XtraDB. If you haven't signed up yet - spaces are still available.
Entry posted by Morgan Tocker | …
[Read more]
First time I heard about Galera on Percona Performance Conference
2009, Seppo Jaakola was presenting "Galera: Multi-Master Synchronous MySQL Replication
Clusters". It was impressed as I personally always wanted it
for InnoDB, but we had it in plans at the bottom of the list, as
this is very hard to implement properly.
The idea by itself is not new, I remember synchronous replication
was announced for SolidDB on MySQL UC 2007, but later the product
was killed by IBM.
So long time after PPC 2009 there was available version mysql-galera-0.6, which had serious flow, to setup a new node you had to take down whole cluster. And all this time Codership ( company that develops Galera) was working on 0.7 release that introduces node propagation keeping cluster online. You can play with 0.7pre release by yourself …
[Read more]I’ve released version 1.1.4 of my improved Cacti templates. Unlike the prior release, which was solely bug fixes, this one includes new graphs in the MySQL template. Some of the graphs are of data that’s exposed in standard MySQL versions, but some of it is available only in Percona’s high-performance builds of the MySQL database server. If you don’t have a Percona build, those graphs will just contain nothing, but there is no detrimental effect.
This template release is fully backwards compatible with the previous release. The upgrade process is to copy the new PHP file into place and import the new template file. You can then add the new graphs to your hosts.
I’ve also taken the opportunity to address many of the other open issues. Most of these were minor, such as a debug …
[Read more]
Ever seen this in SHOW INNODB STATUS and wondered
what it means?
-------------------------------------
INSERT BUFFER AND ADAPTIVE HASH INDEX
-------------------------------------
Ibuf: size 1, free list len 4634, seg size 4636,
I’ve never been quite sure, and Peter didn’t really clarify things himself, so
I took a look at the source. If I’m not mistaken, the seg size is
really one more than the number of records the insert buffer can
hold, the free list length is the number that aren’t in use, and
the size is just seg_size - (1 + free_list_len).
These seem to be kept in lockstep as records are inserted and
merged.
Related posts:
[Read more]I wanted to provide an update on two things:
We love to speak at Meetup groups. If you are an organizer feel free to let us know you are interested. There's no guarantee that we can get schedules to align - but there are a number of Percona consultants that travel regularly.
Entry posted by …
[Read more]
This presentation was be done by Sheeri Cabral of The Pythian
Group and went into how to use SHOW ENGINE INNODB
STATUS to get more information about your Innodb tables,
foreign keys and transactions. This is a great presentation to
learn how InnoDB works.
It also went through how to use SHOW ENGINE INNODB
STATUS to tune several InnoDB variables:
innodb_adaptive_hash_index
innodb_commit_concurrency
innodb_concurrency_tickets
innodb_file_io_threads
innodb_log_buffer_size
innodb_max_purge_lag
innodb_sync_spin_loops
innodb_thread_concurrency
innodb_thread_sleep_delay
The slides can be downloaded from:
http://technocation.org/files/doc/ShowEngineInnoDBStatus.pdf
(Note that the slides open up to the middle section, which …
[Read more]