The latest from the MySQL community

MySQL 9.7 Community Edition now includes the hypergraph optimizer as an alternative to the classic join optimizer, making this capability available across all MySQL editions. This is not a cosmetic change. The hypergraph optimizer uses a new join-planning framework aimed at queries where plan shape can make a real difference, particularly for multi-table joins, workloads […]

When vertical scaling, read replicas, and MEMORY tables weren't enough, Readyset's SQL-level caching broke through the ceiling, delivering over 109,000 queries per second on MySQL.

Key Results

109K

Queries Per Second

0

Lines of Code Changed

<1ms

Cached Query Latency

8x

Read Throughput Increase

About Lemit

Lemit (Lemit Tecnologia da Informacao) is a Brazilian data enrichment and credit intelligence company based in Sao Paulo. Their platform enables businesses to make faster, more accurate credit decisions by enriching, qualifying, and cleansing customer data at scale, powering individual lookups, batch integrations, and real-time API queries across millions of records with 100% all-flash storage.

"Using Readyset with our existing …

When people ask me how to tune MySQL, they usually mean, “Which variables should I change in my.cnf?” (the MySQL configuration file) That certainly is a reasonable place to start, because most day-to-day performance tuning really is driven by MySQL itself: memory allocation, redo flushing, connection handling, temporary tables, and InnoDB I/O behavior. But the […]

As an update to our recent blog post, “Where can you find MySQL next? (Updated events list for March–May 2026)” we’d like to share the latest confirmed MySQL events and webinars, including newly added ones plus refreshed details for sessions we already announced. Since plans and agendas evolve quickly, this post is intended to provide […]

As part of our MySQL community engagement plan, which includes delivering new features into MySQL Community Edition, increasing collaboration and transparency, and expanding and growing the MySQL Ecosystem, we have created a new rhythm of public MySQL Community Discussions—starting with our first session on February 25 and continuing with our second session on March 23, […]

You ship a query on Monday. It runs in 2 ms. Six months later, the same query — same SQL, same indexes — takes 4 seconds. Nothing changed. Except one thing did: the table grew.

Welcome to the everyday problem Big O was invented to describe. This post is a practical, MySQL-flavoured tour of time complexity. We’ll keep the math light, the pictures clear, and we’ll finish with the exact algorithms your database uses to keep your queries fast (or slow).

What is Big O, really?

Forget seconds. Big O is not a unit of time. It’s a way of describing how the cost of an algorithm grows as the input grows. Specifically: if you double the data, does the work double? Stay the same? Quadruple? That shape is the algorithm’s complexity.

We call the input size n. A few shapes come up over and over in real systems:

• O(1) — …

Production data is invaluable for day-to-day operations—support, troubleshooting, analytics, and development. But when that data contains sensitive fields such as SSNs, emails, phone numbers, or other identifiers, broad read access can quickly become unnecessary exposure.  Just as importantly, many organizations operate under regulatory and contractual requirements that expect strong controls around access to sensitive data—often including data masking as […]

Production data is invaluable for day-to-day operations—support, troubleshooting, analytics, and development. But when that data contains sensitive fields such as SSNs, emails, phone numbers, or other identifiers, broad read access can quickly become unnecessary exposure.  Just as importantly, many organizations operate under regulatory and contractual requirements that expect strong controls around access to sensitive data—often including data masking as […]

MySQL 9.7.0 LTS landed today, and we had the pleasure of watching the announcement live — and we were the first ones to download. If you've already pulled the binaries and you're poking at it in a lab, here's the news: Readyset already supports it.

The point isn't that Readyset happens to work with 9.7. The point is that we were prepared for the launch. Our compatibility matrix has been running 9.7 pre-release builds, so the same readysettech/readyset:latest image you can docker pull right now already accepts 9.7 as an upstream. Today's job is to prove it, not to port it.

Step 1 - Register MySQL 9.7 as an rdst target

rdst stores connection profiles in ~/.rdst/config.toml. One non-interactive command adds the target, and the …

MySQL is extending caching_sha2_password to support PBKDF2 with SHA-512 as a new password storage format. This is a meaningful step forward for password security because it strengthens stored password transformations without requiring a new authentication plugin, without breaking clients, and without forcing an all-at-once migration. Existing accounts continue to work, new passwords can use the stronger format, and administrators […]