MySQL’s default storage engine as of version 5.5 is InnoDB. InnoDB maintains a storage area called the buffer pool for caching data and indexes in memory. By keeping the frequently-accessed data in memory, related searches are retrieved much faster than reading from disk.

When you stop or restart MySQL, you lose the cached data stored in the buffer pool. There is a feature in MySQL 5.6 which allows you to dump the contents of the buffer pool before you shutdown the mysqld process. Then, when you start mysqld again, you can reload the contents of the buffer pool back into memory. You may also …

There are generally three components to any benchmark project:

1. Create the benchmark application
2. Execute it
3. Publish your results

I assume many people think they want to run more benchmarks but give up since step 2 is extremely consuming as you expand the number of different configurations/scenarios.

I'm hoping that this blog post will encourage more people to dive-in and participate, as I'll be sharing the bash script I used to test the various compression options coming in the MongoDB 3.0 storage engines. It enabled me to run a few different tests against 8 different configurations, recording insertion speed and size-on-disk for each one.

If you're into this sort of thing, please read on and provide any feedback or improvements you can think of. …

When we launched repos for SUSE Linux 11 back in December, we said we would be adding SUSE 12 support as soon as possible, and we are happy to announce that as of last week the repo offers MySQL Server packages for SUSE 12. It did take us a little bit of extra time to get this […]

In a previous post, titled “Multi-threaded replication with MySQL 5.6: Use GTIDs,” I explained that using GTID replication is almost a requirement when using MySQL 5.6 MTS. Let’s see now how to perform the day-to-day operations when MTS and GTIDs are both enabled. (I’ll also be presenting a related webinar next week titled “Multi-threaded Replication in MySQL 5.6 and 5.7″).

Seeing the execution gaps

If you have a look at SHOW SLAVE STATUS while the slave is running, you may not be expecting such an output:

[...]
Executed_Gtid_Set: …

On Wednesday, February 25 at 18:00 CET (9 am Pacific Time), I will do webinar on how to analyze and tune MySQL queries for better performance.

The webinar covers how the MySQL optimizer chooses a specific plan to execute SQL queries. I will also show you how to use tools such as EXPLAIN (including the new JSON-based output) and Optimizer Trace to analyze query plans. We will also review how the Visual Explain functionality available in MySQL Workbench helps us visualize these plans. The webinar will also contain several examples of how to take advantage of the query analysis to improve performance of MySQL queries.

The presentation will be approximately 60 minutes long followed by Q&A.

For details on how to register for the webinar visit  …

Thanks Mark, this makes it so much easier!

Hi Keith,

Thanks for blogging about MEM and the bulk add feature. I thought you might like to know, that for an environment like yours, there’s an even *easier* way to configure this. MySQL Enterprise Monitor also has an “automatically monitor after process discovery” feature that works as long as you have credentials that are the same on all of your instances (which in your case, they are). Go to Configuration -> Advisors, then open the “Monitoring and Support Services” category, and expand it. Click on the drop-down menu for the “MySQL Process Discovery” entry, and choose “Edit Advisor Configuration”. Answer “Yes” for the “Attempt Connection” choice, and the rest is similar to the add/edit connection dialog. Once this is configured, any time a MEM agent discovers a MySQL process that MEM isn’t monitoring, it will first attempt to use this stored set of credentials to setup monitoring of that instance.

Carrying on with my MySQL 5.7 Labs Multi Source Replication scenario, I wanted to evaluate performance impact via MySQL Enterprise Monitor.

Whilst I opened my environment, I remember that I had generated lots of different skeleton scripts that allowed me to deploy the 50 servers quickly, and I didn’t want to add each of my targets 1 by 1 in MEM. So, I used one of the many features available, “Add Bulk MySQL Instances”.

So, I’ve got 50 (3001-3050) masters but only 1 slave (3100).

By default, MEM monitors it’s own repository, i.e. the 1/1 server being monitored in the All group.

I want to add my slave in first, because that’s how I’m organizing things, and I’ll take the opportunity to create the monitoring group I want to …

We’re delighted to announce a ClusterControl Template for Zabbix, so Zabbix users can now get information about the status of their database clusters, backups and alarms. We have previously published integrations with other monitoring systems including Nagios and PagerDuty.

This template is built using the ClusterControl REST API to retrieve monitoring data. Thus, you need to have a ClusterControl API token and URL configured in the template’s configuration file. This simplifies the initial configuration, and allows users to extend the current monitoring data.

…

WebAssign develops higher education online instructional tools for faculty and students, and more than one million students at over 2,300 educational institutions use WebAssign each year. Last year, WebAssign experienced a large outage that impacted their ability to provide timely online grading and assessments; they took this opportunity to look for new tools that would improve insights into their database activities and ensure service level requirements.

“MEM for MySQL wasn’t able to provide per-query metrics or fault diagnosis, which is a level of detail that we value,” said Valerie Parham, DBA, WebAssign. “Instead, releases would appear fine, but then a problem would pop up and we’d have to do a hot-fix so it didn’t turn into an outage, which placed undue stress on everyone.”

WebAssign looked at a number of solutions, including Percona Cloud Tools, but none offered the same level of full query insight and …