This post is the next part following the initial article about MySQL 5.6 vs 5.5 benchmark results (and MySQL 5.6 scalability).

The focus in this article is on the "tuning impact" used during the published tests, and also I have for you few more test results to present which were missed initially -- Sysbench tests using 8 tables instead of a single one (as it does by default).

All my.conf setting I've used during the tests was already presented within an initial article, so let's go directly to details about special tuning setting. While many parameters are pretty important (like use or not use O_DIRECT, choose a right REDO log and Buffer Pool size, flush or not …

MySQL uses the concept of SQL_MODE to "define what SQL syntax MySQL should support and what kind of data validation checks it should perform". This post is about one of those modes, ONLY_FULL_GROUP_BY, and why I use it.

Roland Bouman wrote a great post a few years ago that debunks some myths about using GROUP BY in MySQL. His post has a lot of detail and examples, and does a very good job detailing the way GROUP BY works in MySQL with and without ONLY_FULL_GROUP_BY enabled. I recommend that you go and read that post now. Among other things, Roland points out one case where query performance is improved by …

ClearStory sheds light on data analysis service. Illuminating ‘dark data’. More.

For 451 clients: ClearStory bags $9m in series A funding, sheds light on its data analysis service bit.ly/Y6v8sV By Krishna Roy

— Matt Aslett (@maslett) February 12, 2013

For 451 clients: Global IDs makes ‘big data’ MDM play via cloud and Hadoop, touts profitable growth bit.ly/Y6v6kL By Krishna Roy

— Matt Aslett (@maslett) February 12, 2013

ScaleBase releases version 2.0 of its MySQL database scalability software bit.ly/WGtEtN

— Matt Aslett (@maslett) …

With TokuDB v6.6 out now, I’m excited to present one of my favorite enhancements: fast updates with TokuDB. Update intensive applications can have their throughput limited by the random read capacity of the storage system. The cause of the throughput limit is the read-modify-write algorithm that MySQL uses when processing update statements. MySQL reads a row from the storage engine, applies the updates to it, and then writes the new row to the storage engine. To address this throughput limit, TokuDB uses a different update algorithm that simply encodes the update expressions of the SQL statement into tiny programs that are stored in an update Fractal Tree® message. This update message is injected into the root of the Fractal Tree index. …

I’ve been woefully neglectful of my responsibilities to post regularly about Percona Live MySQL Conference and Expo 2013 (PLCME 2013), but here’s some highlights of what I am planning to attend from the schedule.  Read to the very bottom for the chance to win a free full pass to the conference!

When picking talks to attend, I typically try to balance sessions that will fill in gaps in my knowledge (especially with topics that have come up repeatedly) with sessions on topics that I already specialize in to gain more depth.  Once I’m at a conference, I often will change my plans at the last minute, but here’s what I’d choose today:

Tutorial Day

I’m giving my own all-day tutorial on …

New Version of Data Traffic Manager Supports Infinite Application Scalability, a Sleek New Look and Easier-than-Ever Deployment BOSTON – February 12, 2013 — ScaleBase, the company that keeps next gen apps and business-critical databases up-and-running, just released Data Traffic Manager 2.0.  It’s the only database scalability software that solves the three biggest challenges next-gen apps face [...] Read More

Wanting to give away the pass at all costs, Shlomi then published a new post, …

MySQL Tech Tour: From the Web to the Cloud
Thursday, 21 February 2013, Oslo Norway

Are you looking to deploy MySQL-based applications either on-premise or in the cloud?
Join us to learn how you can reduce costs and improve business agility while achieving the highest levels of MySQL scalability, security and uptime.

We will help you better understand:

• Why MySQL has become the leading database in the cloud, and how it addresses the critical attributes of cloud-based deployments
• How ISVs can power their SaaS offerings with MySQL
• What are the best practices to deploy the world’s most popular open source database in public and private clouds

You will also find out:

• How you can leverage MySQL together with Hadoop and other technologies to unlock the value of Big Data, either on-premise or in the …

I had an interesting conversation about table functions in Oracle’s PL/SQL; and the fact that they’re not available in MySQL. When I explained they’re available in Microsoft T-SQL User-Defined Functions (UDFs), my students wanted a small example. One of them said they’d tried to do it but couldn’t get it to work because they found the Microsoft web pages difficult to read and use. Specifically, they didn’t like the sparseness of this one on how to create a function.

Here’s a quick definition of a UDF table function that runs in the studentdb schema (created in this post for migrating SQL Server into a MySQL database). The following getConquistador function takes a single string, which acts to filter the result set …

The log files of any applications (LAMP) like apache, mysql, linux, php  needs to be managed, if they are growing frequently on linux servers. Managing log file efficiently, prevents from high disk space utilization.

Logrotate is one of the functionality, available on all the linux based servers to manage log files. This tool rotates, compresses, and mails system logs

Configuration files: /etc/logrotate.conf

        # see "man logrotate" for details
        # rotate log files weekly
        weekly
        # keep 4 weeks worth of backlogs
        rotate 4
        # create new (empty) log files after rotating old ones
        create
        # uncomment this if you want your log files compressed
        #compress
        # RPM packages drop log rotation information into this directory
        include /etc/logrotate.d
        # no packages own wtmp -- we'll rotate them …