This year I shared results where InnoDB wrote between 10X and 20X
more data to storage than MyRocks for the same workload. I use KB
written to storage per transaction as a measure of write
efficiency and I usually compute this with data from the
benchmark client and iostat. I get KB written/second from iostat,
average transaction/second from the benchmark client and divide
the former by the latter to compute KB written/transaction. When
using SSD this excludes the writes done by SSD firmware and I
previously reported that the overhead was
worse for InnoDB than for RocksDB on one vendor's device.
An engine that writes less to storage per transaction is more
write efficient. It is a good thing if MyRocks writes 10X less to
storage than InnoDB for the same workload. …
As you probably know MySQL is an Open Source product licensed under the GPL v2. The GPL grants you the right to not just read and understand the code of the product but also to use, modify AND redistribute the code as long as you follow the GPL rules.
This redistribution has happened in the past various times. But in the western hemisphere only 3 of these branches/forks of MySQL are of relevance for the majority of the MySQL users: Galera Cluster for MySQL, MariaDB (Server and Galera Cluster) and Percona Server (and XtraDB Cluster).
Now it happened …
[Read more]In 8.0 we have introduced another bunch of parser refactoring worklogs:
- WL#8067 (me): “Refactoring of the CREATE TABLE statement” with its subtasks:
…
Join us on Tuesday, December 6th, for our last webinar of the year. Krzysztof Książek, Senior Support Engineer at Severalnines, will be sharing his top 9 tips on how to best build a production-ready MySQL Replication environment.
MySQL replication is a well known and proven solution for building distributed setups of databases, and it has gone through a total transformation with version 5.6 and more recently, 5.7. Although straight-forward to deploy, a production-ready setup requires a bit of planning and preparation. What does a good replication configuration look like? How do you ensure performance? What do you do when a topology is broken, and replication will not restart? How to perform schema changes?
So if you'd like to learn what is needed to build a stable environment using MySQL replication, this webinar is for you!
Top 9 Tips for building a stable MySQL Replication environment
Tuesday, December 6th …
[Read more]Happy Thanksgiving!
This week is all about savings. If you have seen offers all around you, well… digest this before you dig into that turkey.
A never before offer, flat 30% discount on SQLyog & Monyog product purchases & upgrades.
Use coupon code: TG30
Hurry up, this offer is valid until 24th November, 23:59 PST.
Are you using SQLyog community edition? It’s the perfect time to upgrade to the commercial version and use powerful tools to save tons of time on a daily basis. Shop here.
Want to become better at monitoring MySQL servers? Experience Monyog – the most secure & scalable MySQL monitoring tool. Know what’s in store for you.
If you’re an …
[Read more]Harry Weller died suddenly this week. Harry was one of the best venture capital investors in history. He led NEA’s investment in my company, VividCortex. Harry was an advocate and mentor to me, but he was more: in both life and death, he reminded me of Alan Rimm-Kaufman, a boss and mentor who died a handful of years ago.
Alan Rimm-Kaufman
Harry isn’t the first person to believe in me and create an amazing opportunity before dying unexpectedly. Before Harry, there was Alan Rimm-Kaufman, who shaped my career tremendously.
I joined Alan in 2006 at the Rimm-Kaufman Group, a bootstrapped startup he founded in Charlottesville, Virginia. Alan had an infectious love of life and was unstoppably energetic. He’d enter a room with his face lit up, bubbling with an idea he couldn’t resist sharing. He was unable to stand still. He hopped around like a soccer goalie.
Alan would start a thought and someone else would …
[Read more]
I used sysbench to understand the impact of transaction isolation
and the performance schema for InnoDB from upstream MySQL
5.6.26.
The test server has 24 CPU cores, 48 HW threads with
hyperthreading enabled, 256G of RAM and fast SSD. For sysbench I
used the 1.0 version with support for Lua. Tests were run
in two configurations -- cached and IO-bound. For the cached
configuration I used 8 tables, 1M rows/table and the database
cache was large enough to cache all data. For the IO-bound
configuration I used 8 tables, 10M rows/table, a 2G database
cache and buffered IO so that all data was in the OS page cache.
The database was ~2G for the cached configuration and ~20G for
the IO-bound configuration. InnoDB table compression was not used
and jemalloc was used. The binlog was enabled but sync-on-commit
was disabled for the binlog and InnoDB redo log.
With 8 …
Whether for a maintenance, applying non dynamic config changes,
MySQL upgrade or other many reasons, a MySQL shutdown/restart is
required.
In this post I’ll list some of the best practices before shutting
MySQL down to make it clean and fast which in turn, will lead to
fast and safe start!
-
Double check the instance you are going to
shutdown!!
First of all, and before doing anything confirm first the instance you are going to shutdown. You definitely, don’t want to shutdown a wrong MySQL instance by mistake, especially, when you’re working on production environments. -
Stop Replication:
Although MySQL stops the replication automatically in the shutting down process but if it didn’t stop for any reason before the timeout is reached, it will be killed. So, if that server is a slave, it’s better to stop the replication threads first …
Percona announces the release of Percona Server 5.5.53-38.4 on November 18, 2016. Based on MySQL 5.5.53, including all the bug fixes in it, Percona Server 5.5.53-38.4 is now the current stable release in the 5.5 series.
Percona Server is open-source and free. You can find release details in the 5.5.53-38.4 milestone on Launchpad. Downloads are available here and from the Percona Software Repositories.
Removed Features:
- …
Galera Clusters are generally meant to run non-stop, so shutting down the entire cluster is not required during normal operation. Yet, if there is a need to perform such a procedure, it is likely that it will be happening under pressure, so it is important for it to complete safely and as quickly as possible in order to avoid extended downtime and potential data loss.
Galera 3.19 includes two important improvements to whole-cluster restart: the “Safe-to-Bootstrap” protection and Gcache recovery. In this article, we will describe the first feature.
Whole-Cluster Restart
First, a few words on cluster restarts in general. Regardless of whether it was an orderly shutdown or a sudden crash of all nodes, restarting the entire cluster is governed by the following principles:
- Since the old cluster no longer logically exists, a new logical cluster is being created
- The first node that is being started …