Recently we had a report from a user who had seen a stunning 90% performance regression after upgrading his server to a Linux kernel with KPTI (kernel page-table isolation – a remedy for the Meltdown vulnerability). A big deal of those 90% was caused by running in an old version of VMware which doesn’t pass […]
The post MyISAM and KPTI – Performance Implications From The Meltdown Fix appeared first on MariaDB.org.
As promised, the following are links to slides from my talks during MySQL Day and FOSDEM @Brussels in Feb.2018 :
NOTE : for those who did not follow, CATS is not the only change in InnoDB ;-))
Rgds,
-Dimitri
Let’s look at some of the most popular Percona Database Performance Blog posts in 2017.
The closing of a year lends itself to looking back. And making lists. With the Percona Database Performance Blog, Percona staff and leadership work hard to provide the open source community with insights, technical support, predictions and metrics around multiple open source database software technologies. We’ve had over three and a half million visits to the blog in 2017: thank you! We look forward to providing you with even better articles, news and information in 2018.
As 2017 moves into 2018, let’s take a quick look back at some of the most popular posts on the blog this year.
Top 10 Most Read
These posts had the most number of views (working down from the highest):
…
[Read more]In this blog post I’ll look at the performance of Percona XtraDB Cluster on AWS using different service instances, and recommend some best practices for maximizing performance.
You can use Percona XtraDB Cluster in AWS environments. We often get questions about how best to deploy it, and how to optimize both performance and spend when doing so. I decided to look into it with some benchmark testing.
For these benchmark tests, I used the following configuration:
We …
[Read more]
This post is following the story of MySQL 8.0 Performance &
Scalability started with article about 2.1M QPS obtained on Read-Only workloads. The
current story will cover now our progress in Read-Write
workloads..
Historically our Read-Only scalability was a big pain, as
Read-Only (RO) workloads were often slower than Read-Write
(sounds very odd: "add Writes to your Reads to go faster", but
this was our reality ;-)) -- and things were largely improved
here since MySQL 5.7 where we broke 1M QPS barrier and reached
1.6M QPS for the first time. However,
improving Writes or mixed Read+Writes (RW) workloads is a much
more complex story..
What are the main scalability show-stoppers …
The first release candidate of MySQL 8.0 is here,
and I'm happy to share few performance stories about. This
article will be about the "most simple" one -- our in-memory
Read-Only performance ;-))
However, the used test workload was here for double reasons :
Going ahead to the second point, the main worry about New
Sysbench was about its LUA overhead (the previous version 0.5 was
running slower than the old one 0.4 due LUA) -- a long story
short, I can confirm now that the New Sysbench is running as fast
as the oldest "most lightweight" Sysbench binary I have in use !
so, KUDOS Alex !!! ;-)) …
In my previous blog post, I talked about new general tablespaces in MySQL 8.0. Recently MySQL 8.0.3-rc was released, which includes a new data dictionary. My goal is to create one million tables in MySQL and test the performance.
Background questions
Q: Why million tables in MySQL? Is it even realistic? How does this happen?
Usually, millions of tables in MySQL is a result of “a schema per customer” Software as a Service (SaaS) approach. For the purposes of customer data isolation (security) and logical data partitioning (performance), each “customer” has a dedicated schema. You can think of a WordPress hosting service (or any CMS based hosting) where each …
[Read more]Welcome to another post in our series of interview blogs for the upcoming Percona Live Europe 2017 in Dublin. This series highlights a number of talks that will be at the conference and gives a short preview of what attendees can expect to learn from the presenter.
This blog post is with Alexey Kopytov, sofware developer and maintainer of sysbench. His talk is Modern sysbench: Teaching an Old Dog New Tricks. His presentation present new features provided by recent releases and explain how they can be used to create complex benchmark scenarios and collect performance metrics with a simple Lua API. It will also run a live demo of some of …
[Read more]In this blog post, I will look at disk utilization and saturation.
In my previous blog post, I wrote about CPU utilization and saturation, the practical difference between them and how different CPU utilization and saturation impact response times. Now we will look at another critical component of database performance: the storage subsystem. In this post, I will refer to the storage subsystem as “disk” (as a casual catch-all).
The most common tool for command line IO performance monitoring is
iostat
, which shows information like this:
root@ts140i:~# iostat -x nvme0n1 5
Linux 4.4.0-89-generic (ts140i) 08/05/2017 _x86_64_ (4 CPU)
avg-cpu: %user %nice %system %iowait %steal %idle
0.51 0.00 2.00 9.45 0.00 88.04
Device: rrqm/s wrqm/s …[Read more]
In this blog post, I will run a gh-ost benchmark against the performance of pt-online-schema-change.
When gh-ost came out, I was very excited. As MySQL ROW replication became commonplace, you could use it to track changes instead of triggers. This practice is cleaner and safer compared to Percona Toolkit’s pt-online-schema-change. Since gh-ost doesn’t need triggers, I assumed it would generate lower overhead and work faster. I frequently called it “pt-online-schema-change on steroids” in my talks. …
[Read more]