Please turn JavaScript on
Percona Database Performance Blog icon

Percona Database Performance Blog

Receive updates from Percona Database Performance Blog for free, starting right now.

We can deliver them by email, via your phone or you can read them from a personalised news page on follow.it.

This way you won't miss any new article from Percona Database Performance Blog. Unsubscribe at any time.

Site title: Percona – The Database Performance Experts

Is this your feed? Claim it!

Publisher:  Unclaimed!
Message frequency:  0.68 / day

Message History

It was quite challenging to perform postgres major upgrade, e.g., v17 to v18, in a Percona operator/K8s environment. There was no convenient approach to accomplish this task. The only viable solutions left were a Manual Dump/Restore to a new environment or using Logical replication. 

But these options were not free from challenges. Procuring a new ...


Read full story

In my previous post I said that MongoDB published some impressive numbers for 9.0, but I couldn’t find any details about how the tests were done. I ended with “always run your own benchmarks”. So I figured I should follow my own advice.
Let me be clear u...


Read full story
MySQL and DuckDB

Unlike row-oriented databases, which store data for a single record sequentially on disk, favoring single-row lookups, columnar databases store all the values from a column contiguously in storage, allowing only the selected column to be read from disk.

The default MySQL engine is InnoDB, which is ACID-compliant and great for OLTP (Online Transaction P...


Read full story

Percona Search for MongoDB 1.70.5-3 is now Generally Available and supported for production use. You can now easily run full-text, vector, and hybrid searches with automatic embedding on production Percona Server for MongoDB deployments. The release also adds the Hugging Face Inference API as a new automatic embedding provider.

In this blog post, I cover why search now...


Read full story
An alternative to sharding a MongoDB replica set that outgrew its memory: a proof of concept

A replica set that no longer fits in memory

Most MongoDB replica sets start small. The working set fits in the WiredTiger cache, reads come from memory, and nobody thinks about disks. Then the data keeps growing. Orders, events and logs pile up for years, and one...


Read full story