Introduction As I already mentioned, you should never use the TABLE identifier generator since it does not scale properly. In this post, I’ll show you why you should not rely on the AUTO GenerationType strategy if you’re Hibernate application uses MySQL. Prior to Hibernate 5 On Hibernate 4, if you had the following entity mapping: … Continue reading Why should not use the AUTO JPA GenerationType with MySQL and Hibernate →
10 Older Entries »
Please join Laurynas Biveinis, Percona’s Technical Director – Engineering, on January 25, 2017, at 7 am EST (UTC-8) as he discusses “Percona Server for MySQL 5.7: Key Performance Algorithms.”
In this webinar, Laurynas will discuss selected areas of InnoDB and Percona Server for MySQL 5.7 internals as they relate to buffer pool management and flushing (from a performance and scalability point of view). He will describe the motivation behind the buffer pool mutex split, multi-threaded LRU flusher and parallel doublewrite features in Percona Server for MySQL 5.7, given that MySQL InnoDB 5.7 has re-implemented many of the same features found in Percona Server for MySQL – especially …[Read more]
I shared results last week for the insert
benchmark. The test server for that result had fast SSD courtesy
of several NVMe NAND flash devices. I repeated tests on a server
with slower SSD and the results are interesting. Regardless of
the storage device, MyRocks did better when the database was
larger than RAM and InnoDB 5.7.10 did better when the database
fit in RAM. But the difference between MyRocks and InnoDB 5.7.10
for the in memory workload is much smaller on slow SSD than
it is on fast SSD. It is always risky to ignore the context from
benchmark results and the important context here is the
performance of the storage device.
Slower SSD hurts InnoDB more than it hurts MyRocks because MyRocks is more efficient for writes. Spending less IO on writes saves IO to do more writes or more reads as I …
MySQL is available for a huge variety of platforms, in a wide range of packaging formats and through many channels. Part of our mission is to keep up with the times by making sure that all MySQL products are available where people expect and need them to be. As part of that we have invested […]
In my previous post I've presented a list of bugs reported by famous MySQL developers, DBAs, users and support engineers who used oprofile to find the problem or root cause of the problem they studied. I assume that some of my readers would like to follow their steps and try to use this tool while working on MySQL performance problems. Bug reports I mentioned contain outputs and, rarely, just some commands used. That's why I decided to write a kind of a basic "Howto" document. The tool does have a detailed enough manual, but few basic steps for quick use of oprofile to study MySQL-related problems should still help. At least I had always considered …[Read more]
In my previous post, we saw the usage of MySQL Group Replication (MGR) in single-primary mode. We know that Oracle does not recommends using MGR in multi-primary mode, but there is so much in the documentation and in presentations about MGR behavior in multi-primary, that I feel I should really give it a try, and especially compare this technology with the already existing multiple master solution introduced in 5.7: multi-source replication.
To this extent, I will set up two clusters using MySQL-Sandbox. The instructions for MGR in …[Read more]
Users had to identify the reasons for MySQL performance problems
somehow well before famous Performance Schema appeared in MySQL 5.5.3,
and even before Domas invented his Poor Man's Profiler. Poor users had
to use some OS-level tools, and among these tools the most
important one was, probably, oprofile.
oprofile is a system-wide statistical profiling tool for Linux available since 2001 and 2.4.x kernels. It was applied to MySQL for many …
Several customers and other people from the open source community have asked us how they could make their own Percona Server for MySQL RPM binaries from scratch.
This request is often made by companies that want to add custom patches to our release. To do this, you need to make some modifications to the
file in the source tree, and some preparation is necessary.
This post covers how you can make your own RPMs from GIT or source tarball so that you can build RPMs from your own modified branch, or by applying patches. In this example, we’ll build Percona Server 5.7.16-10.
Making your own RPMs is not a recommended practice, and should rarely be …[Read more]
Monitoring MariaDB with the All New Monyog v7.0 julienfritsch Fri, 01/20/2017 - 11:02
MariaDB monitoring tool, Monyog, provides insights into server performance with a customizable dashboard. Webyog just announced the launch of the new Monyog v7.0! With this new release, MariaDB customers will get access to a completely revamped Monyog user interface and industry-leading feature additions to uncover valuable server performance insights, including:
- Monitor Top 10 Queries Across All Servers – Save time and resources with an extensive view of the state of MariaDB servers under one roof.
- Customizable Dashboard and Enhanced Chart Performance – Choose to create and customize monitoring dashboards, and enable or disable MySQL and system charts, to best analyze your server performance.
- Replication Topology View – Gain visibility into the replication hierarchy of servers along with the details of each …
As you know pre-FOSDEM MySQL Day will take place on Friday February 3rd in Brussels. During this day dedicated to MySQL and focusing on 8.0, Norvald will be on stage at 16.50 to check if you are ready for MySQL 8.0’s GIS implementation.
Many great things are happening to GIS in MySQL 8.0. But in order to move forward, we also have to break legacy behavior. What will change? How? Why? And what can I do to avoid problems when I upgrade?
Join Norvald for a tour of changes and recommendations that you
can start following today to make your data and applications
ready for the future.
10 Older Entries »