Readyset

Cache invalidation is the problem of knowing when a cached query result has gone stale and needs replacing. A write changes one row in the database, and every cached answer derived from that row is now wrong. The work is finding those answers and dropping

Readyset now serves 4.3 million queries per second from a single node, over 6x higher than the previous release and nearly 3x faster than MySQL on the same hardware.

August moved fast around here, and we've got a full roundup for you. Cut Database Infra with Self-Tuning Caching On August 18, our team hosted a live session on what changes when caching moves into your infrastructure and continuously tunes itself. They c

This post extends Readyset's query rewrite pipeline - the machinery that turns arbitrary SQL into a form the dataflow engine can compile - to a family of query shapes it used to reject outright. It follows an earlier post, How Readyset Rewrites Your SQL,

We had an eventful July and have exciting news to share! The Readyset Platform Your laptop is full of caches that manage themselves; you never manually tune them, set invalidation logic, or worry about the wrong result. Database caching has traditionally

F.32. pg_stat_statements - track statistics of SQL planning and execution # F.32.1. The pg_stat_statements View F.32.2. The pg_stat_statements_info View F.32.3. Functions …

Readyset's shallow caches make a number of improvements over typical TTL-based caches. Typical TTL-based caches force a coarse grained decision upon you for your entire workload. On the one hand, picking a TTL lets your workload benefit from the speed of

Long story short. A memory shortage is repricing the hardware under every cloud database. Conventional DRAM contract prices rose 93% to 98% in a single quarter, and it lands on your bill: a memory-optimized database instance near $386 a month today is on

Your laptop is full of caches you have never once thought about. There are several in the CPU, each one orders of magnitude faster than the last, one in the memory controller, one in the operating system's page cache, one on the disk itself, another in yo

Read traffic climbs, the primary starts to sweat, and the fix everyone reaches for is the same one: spin up another read replica. It is the path of least resistance, it is well-documented, and it works often enough that it has become a reflex. The trouble