# Supabase — Introducing DBArena: open, reproducible benchmarks for hosted Postgres

- Company: Supabase (supabase.com)
- Announced: 2026-10-30
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://supabase.com/blog/introducing-dbarena
- Record: https://forck.live/items/30039-introducing-dbarena-open-reproducible-benchmarks-for-hosted-postgres
- Subject: Supabase
- Pricing: tpm/$: transactions per minute per dollar of monthly cost, using public on-demand list prices with no discounts.

Supabase is announcing DBArena, a site that publishes reproducible benchmarks of hosted Postgres providers, with Supabase sponsoring the project and releasing the methodology and tooling as open source. The first results compare Supabase Postgres with default storage, Supabase Postgres with OrioleDB, Amazon RDS and Google Cloud SQL at up to seven compute tiers, measured on throughput, price-performance and latency. Supabase says most published database benchmarks come from vendors, use mismatched instance sizes and tuned configurations, and are hard to reproduce, so DBArena runs every provider on the same workload at matched vCPU counts and I/O configuration with each provider's defaults, normalizing results for cost. Each product is tested in a cache-fit scenario, where the data set fits in memory with a buffer cache hit ratio of at least 99%, and a cache-exceeding scenario, where the data set is four times larger than available RAM. Results report average transactions per minute over a 60-minute run, transactions per minute per dollar of monthly cost using public on-demand list prices with no discounts, and p95 latency. The workload is derived from TPC-C with think time disabled, and DBArena states it is not comparable to published TPC-C results because the implementation does not comply with all TPC-C requirements. The first round covers 62 published results drawn from more than 750 individual runs measured between September 25 and October 1, 2026, and went live on October 2 when DBArena launched at Supabase Select. Supabase lists limitations including a single workload, no think time, one region per cloud, list prices, matching by vCPU rather than memory, and load generator placement that is zone-matched on RDS and Cloud SQL but only region-matched on Supabase.

## Evidence

Verbatim from https://supabase.com/blog/introducing-dbarena:

> We're announcing DBArena , a site that publishes benchmarks of hosted Postgres providers. The first results compare Supabase Postgres (with default storage), Supabase Postgres (with OrioleDB), Amazon RDS, and Google Cloud SQL at up to seven compute sizes, measured on throughput, price-performance, and latency.
> 
> Supabase sponsors DBArena. The methodology is public, and all tools to run the benchmarks are open source. Each result includes a raw data file with the exact commands, configuration, and captured meta data, so you can rerun any test and compare your results with published ones.
> 
> Why we built DBArena #
> 
> Most published database benchmarks come from vendors and are difficult to compare with each other. They use different instance sizes, tuned configurations on one side and defaults on the other, and are hard to reproduce. Many report performance metrics without considering price, which hides the tradeoff teams care about.
> 
> On DBArena, every provider runs the same workload at matched vCPU counts and I/O configuration, and results are normalized for cost. Settings stay at each provider’s defaults.
> 
> What DBArena measures #
> 
> The first release covers four products:

---

Record: https://forck.live/items/30039-introducing-dbarena-open-reproducible-benchmarks-for-hosted-postgres
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md