https://github.com/capaj/compare-planetscale-neon-turso
few tiny benchmarks on latencies for the most prominent serverless DBs
https://github.com/capaj/compare-planetscale-neon-turso
drizzle-orm neondb planetscale turso
Last synced: about 1 year ago
JSON representation
few tiny benchmarks on latencies for the most prominent serverless DBs
- Host: GitHub
- URL: https://github.com/capaj/compare-planetscale-neon-turso
- Owner: capaj
- Created: 2024-02-15T13:19:18.000Z (over 2 years ago)
- Default Branch: master
- Last Pushed: 2024-04-28T21:06:19.000Z (about 2 years ago)
- Last Synced: 2025-03-28T17:01:46.679Z (over 1 year ago)
- Topics: drizzle-orm, neondb, planetscale, turso
- Language: TypeScript
- Homepage:
- Size: 386 KB
- Stars: 21
- Watchers: 2
- Forks: 2
- Open Issues: 0
-
Metadata Files:
- Readme: readme.md
Awesome Lists containing this project
README
# Serverless DB latencies comparison
comparison made between three serverless DB offerings:
- planetscale
- neon
- turso
neon and turso are using the hobby plan.
planetscale is the scaler pro plan as I was unable to get the hobby plan in time of testing. Will update this chart when I get access to it.
TODO measure again with neon HTTP driver and upload a proper chart.
## Stack and infrastructure
all DBs were tested in Frankfurt region.
Stack:
- drizzle orm
- cloudflare workers
Neon is using the connection pooler as advised by their docs for serverless environments.
## Conclusions
planetscale seems to have their networking stack setup the best. Their max latency for the simple select query stayed below 67 ms throughout whole test.
Neon is predictable once the instance wakes up, but much slower.
Turso is as fast as PS at times, but has random spikes to 400 ms.