lp:~tmathiasen/mysql-server/mysql-5.5-fio

Created by Torben Mathiasen on 2013-04-30 and last modified on 2013-04-30

This is a version of stock MySQL 5.5 with transparent atomics support. This feature will guarantee full atomicity when writing 16K table space pages and thus doesn't require the use of a double write buffer. The end result is 2x the flash endurance, 20-70% throughput and 2-4x latency improvements (TPCC and sysbench transaction injection respectively).

Get this branch:
bzr branch lp:~tmathiasen/mysql-server/mysql-5.5-fio
Only Torben Mathiasen can upload to this branch. If you are Torben Mathiasen please log in for upload directions.

Branch merges

Related bugs

Related blueprints

Branch information

Owner:
Torben Mathiasen
Project:
MySQL Server
Status:
Development

Recent revisions

4149. By root <root@atg08> on 2013-04-30

Fusion-io transparent atomics support

4148. By Balasubramanian Kandasamy on 2013-01-16

Removed Conflicts: mysql-libs mysql-libs-advanced from spec file

4147. By Bjorn Munch on 2013-01-15

A bit more intelligent processing of .in files in mysql-test/collections

4146. By Olav Sandstaa <email address hidden> on 2013-01-15

Fix for Bug#14636211 WRONG RESULT (EXTRA ROW) ON A FROM SUBQUERY
                     WITH A VARIABLE AND ORDER BY
        Bug#16035412 MYSQL SERVER 5.5.29 WRONG SORTING USING COMPLEX INDEX

This is a fix for a regression introduced by Bug#12667154:
Bug#12667154 attempted to fix a performance problem with subqueries
that did filesort. For doing filesort, the optimizer creates a quick
select object to use when building the sort index. This quick select
object was deleted after the first call to create_sort_index(). Thus,
for queries where the subquery was executed multiple times, the quick
object was only used for the first execution. For all later executions
of the subquery, filesort used a complete table scan for building the
sort index. The fix for Bug#12667154 tried to fix this by not deleting
the quick object after the first execution of create_sort_index() so
that it would be re-used for building the sort index by the following
executions of the subquery.

This regression introduced in Bug#12667154 is that due to not deleting
the quick select object after building the sort index, the quick
object could in some cases be used also during the second phase of the
execution of the subquery instead of using the created sort
index. This caused wrong results to be returned.

The fix for this issue is to delete the reference to the select object
after it has been used in create_sort_index(). In this way the select
and quick objects will not be available when doing the second phase
of the execution of the select operation. To ensure that the select
object can be re-used for the following executions of the subquery
we make a copy of the select pointer. This is used for restoring the
select object after the select operation is completed.

4145. By Satya Bodapati <email address hidden> on 2013-01-07

Null Merge mysql-5.1 to mysql-5.5

4144. By Nirbhay Choubey <email address hidden> on 2013-01-07

Merge of patch for Bug#16066243 from mysql-5.1.

4143. By Satya Bodapati <email address hidden> on 2013-01-04

Merge Post Fix for BUG#14628410 from mysql-5.1 to mysql-5.5

4142. By Nirbhay Choubey <email address hidden> on 2013-01-04

Merge of patch for bug#16066243 from mysql-5.1.

4141. By <email address hidden> on 2013-01-04
4140. By <email address hidden> on 2013-01-03

Branch metadata

Branch format:
Branch format 7
Repository format:
Bazaar repository format 2a (needs bzr 1.16 or later)
Stacked on:
lp:mysql-server
This branch contains Public information 
Everyone can see this information.

Subscribers