When the performance of your database server starts to decline from general usage, you have several options for optimizing it. One common method for optimizing your MySQL database is through partitioning. In this article, we’ll cover the basics of MySQL partitioning, how to apply partitioning to your database, and we'll discuss how it’s related to sharding. The basics of MySQL partitioning Partitioning is the idea of splitting something large into smaller chunks. In MySQL, the term “partitioning” means splitting up individual tables of a database. When you partition a table in MySQL, the table is split up into several logical units known as partitions, which are stored separately on disk. When data is written to the table, a partitioning function will be used by MySQL to decide which partition to store the data in. The value for one or more columns in a given row is used for this sorting process. MySQL provides several partitioning functions …

Deep dive into MySQL’s connection handling mechanisms for optimal connection pooling and improved concurrency.

Performing an operation is always challenging when dealing with K8s.

When on-prem or DBaaS like RDS or Cloud SQL, it is relatively straightforward to apply a change. You can perform a DIRECT ALTER, use a tool such as pt-osc, or even, for certain cases where async replication is in use, perform changes on replicas and failover.

In this blog post, I’ll provide some thoughts on how schema changes can be performed when running MySQL on Kubernetes

I won’t focus on DIRECT ALTERs as it is pretty straightforward to apply them. You can just connect to the MySQL service POD and perform the ALTER.

But how can we apply changes in more complex scenarios where we may want to benefit from pt-osc, gain better control over the operation, or take advantage of the K8s features?

One convenient way that I’ve found …

Introducing Data Import from Amazon S3 in MySQL HeatWave on AWS

WordPress HTML API | Active Record | SQL Injection. OpenLampTech is a media and content source for PHP, MySQL, and the LAMP stack. Thank you for reading.

The Newsletter for PHP and MySQL Developers

Receive a copy of my ebook, “10 MySQL Tips For Everyone”, absolutely free when you subscribe to the OpenLampTech newsletter.

Help support the newsletter and join a fantastic community of developers when you subscribe to OpenLampTech.

Thank you for reading this post. Please share it with someone else who would enjoy it as well.

Josh Otwell has a passion to grow as a PHP …

Not long ago, multifactor authentication and support for FIDO were added to MySQL. Although the original FIDO authentication has now been deprecated in favor of an improved, FIDO2 authentication mechanism—the Web Authentication (WebAuthn); both share the premise that a user must possess an authentication device and use it to certify that the person is who they claim to be. Connector/J supports both and in this post I will show how the WebAuthn authentication can be used.

This Independent Software Vendor (ISV) Catalog for MySQL HeatWave will enable both customers and partners to easily find 3rd party ISV products and services for MySQL HeatWave.    

A comprehensive continuous integration (CI) and continuous deployment (CP) process should include automated testing of code. In this post, we will discuss how to use GitHub Actions to run tests for Node.js code that interacts with a MySQL database.

Transparent Huge Pages (THP) is a memory management feature in Linux operating systems that aims to enhance system performance. While THP can be beneficial for many applications, enabling it on a database server could have unintended consequences. In this post, we will explore THP, its impact on database servers, and how to disable it for optimal performance and stability.

What are Transparent Huge Pages?

In order to understand THP, we should first start with a brief description of Linux HugePages. The concept of HugePages in Linux has existed for many years, first introduced in 2007. By default, the majority of widely used Linux distributions employ a virtual memory page size of 4KB. However, the inclusion of the HugePages feature allows the Linux kernel to efficiently handle substantial memory pages alongside the standard 4KB size.

In order for an application to utilize HugePages, however, it must explicitly include an …

Where can you find MySQL team in October 2023