Today we are already at the post number ten of the series of articles related to extending MySQL with the Component Infrastructure, the list above will be updated as new articles are published:
A year ago, I blogged about An Unprivileged User can crash your MySQL Server. At the time, I explained how to protect yourself against this problem. A few weeks ago, I revisited this vulnerability in a follow-up post in which I explained the fix, claimed that the MySQL 5.7 default configuration for Group Replication is still problematic, and explained a tuning to avoid the
The most common issue when using row-based replication (RBR) is replication lag due to the lack of Primary keys.
The problem is that any replicated DML will do a full table scan for each modified row on the replica. This bug report explains it more in-depth: https://bugs.mysql.com/bug.php?id=53375
For example, if a delete is executed on the following table definition:
CREATE TABLE `joinit` ( `i` int NOT NULL, `s` varchar(64) DEFAULT NULL, `t` time NOT NULL, `g` int NOT NULL ) ENGINE=InnoDB DEFAULT CHARSET=latin1
With this amount of rows:
mysql> select count(*) from joinit; +----------+ | count(*) | +----------+ | 1048576 | +----------+
The delete being:
mysql> flush status ; mysql> delete from joinit where i > 5 and i < 150; Query OK, 88 rows affected (0.04 sec) …[Read more]
This post is the nine one of a series of articles on extending MySQL with the Component Infrastructure, the list above will be updated as new articles are published:
This post is the eight one of a series of articles on extending MySQL with the Component Infrastructure, the list above will be updated as new articles are published:
Recently we published the first part (m5, m5a, m6g) and
the second part (C5, C5a, C6g) of research
regarding comparing Graviton ARM with AMD and Intel CPU on AWS.
We selected general-purpose EC2 instances with the same
configurations (amount of vCPU in the first part). In the second
part, we compared compute-optimized EC2 instances with the same
conditions. The main goal was to see the trend and make a general
comparison of CPU types on the AWS platform only for MySQL. We
didn’t set the goal to compare the performance of different CPU
types. Our expertise is in MySQL performance tuning. We share
research “as is” with all scripts, and anyone interested could
rerun and reproduce it.
All scripts, …
Guess what? OpenLampTech, the newsletter for PHP/MySQL developers, has a new issue full of great curated content for your reading experience this week. Come on by and read the publication!
Get tailored articles with Refind delivered each day in your inbox. Refind is part of my daily reading habit. Make it part of yours by using my referral link. At no additional cost to you, I will be eligible for a premium subscription with more sign-ups from my link. “The essence of the web, every morning in your inbox. Subscribe for free“
The Newsletter for PHP and MySQL Developers
This latest newsletter issue has a wide range of PHP/MySQL articles covering:
Editors and technical reviewers suggested that I cover how to configure MySQL query metrics in chapter 1 of Efficient MySQL Performance, but I deferred because it was out of scope for the book, which focuses on engineers using MySQL, not DBAs. As such, there’s only a note in chapter 1 that says: “Ask your DBA or read the MySQL manual.” But I’ll cover the topic here because that’s what this blog post series is for: behind the book.
Editors and technical reviewers suggested that I cover how to configure MySQL query metrics in chapter 1 of Efficient MySQL Performance, but I deferred because it was out of scope for the book, which focuses on engineers using MySQL, not DBAs. As such, there’s only a note in chapter 1 that says: “Ask your DBA or read the MySQL manual.” But I’ll cover the topic here because that’s what this blog post series is for: behind the book.
Editors and technical reviewers suggested that I cover how to configure MySQL query metrics in chapter 1 of Efficient MySQL Performance, but I deferred because it was out of scope for the book, which focuses on engineers using MySQL, not DBAs. As such, there’s only a note in chapter 1 that says: “Ask your DBA or read the MySQL manual.” But I’ll cover the topic here because that’s what this blog post series is for: behind the book.