Demo
Run a local sample workload and compare throughput with QueryPilot caching on and off.
The demo starts a local orders database, a QueryPilot router, and Readyset. It runs traffic so you can compare throughput with caching on and off. Docker is required.
This demo tests caching against sample data. To monitor your own database, connect it and turn on monitoring.
What the Readyset Platform is
QueryPilot routes SQL traffic and selects queries to cache. Readyset serves the cached results. The QueryPilot documentation describes the architecture.
What RDST sets up for you
RDST creates and manages the local containers for the orders database, Readyset, and QueryPilot.

The first run downloads container images. Later runs can reuse them.
The environment cleans itself up after an hour, and Shut down demo removes it immediately. Nothing it creates touches any database you've configured.
Running it
Start the demo. RDST pulls the images if it needs to, starts Postgres, loads an orders dataset, and brings up Readyset and QueryPilot in front of it.
Start traffic. A workload runs against the database through both paths, directly to Postgres and through QueryPilot, so the two can be compared under identical load.

Turn QueryPilot on. The Accelerator picks queries to cache according to the policy you choose, creates the Readyset caches, and routes matching traffic to them. The chart marks the moment it takes effect.
Reading the chart
With traffic running and caching off, both paths carry the same load, because every query reaches Postgres either way. QueryPilot is proxying, not yet accelerating.

Switching QueryPilot on changes that. In the run above, throughput through the platform went from matching Postgres to roughly 1.6k queries per second against a 19 qps baseline, and the green line shows the moment the caches came online.
Caching policy decides which queries the Accelerator picks. Most frequent targets the queries that run most often, and Most expensive targets the ones consuming the most database time. Switching between them resets the comparison window and marks the chart, so the effect of each choice is visible separately.
Show per-query detail breaks the same numbers down by query, with hit counts and average latency for each path.

Check per-query detail to see which queries account for the measured change.
Moving on to your own database
- Connect your database.
- Turn on monitoring.
- Expand a query on the Database page and select Benchmark to compare it with a local Readyset cache.
The demo's measurements describe its sample workload. Benchmark your own queries before deciding whether caching helps your application.