benchmarks

supabase engineer here would be happy to answer questions about load testing setup here is the github repo[0] with an app that helps me launch terraforms and k6 and keep track of launches/results [0]https://github.com/supabase/benchmarks

PostgREST is used inside every Supabase project. We have >50K projects now[0], some of them making (tens of) millions of API requests through PostgREST daily. It's a fantastic piece of tech, especially when coupled with PostgreSQL Row Level Security. We have some benchmarks here in case you're concerned about performance: https://github.com/supabase/benchmarks/issues/2 [0] hosted platform. We don't add telemetry to self-hosting

A shoutout to Fastify[1] here. It has lived up to its claim of being one of the fastest Node frameworks from our initial benchmarking. We plan to add the benchmarking scripts to our benchmarking repo[2] soon. The entire Fastify ecosystem (and associated modules like pino) has a focus on performance which is great. For example, the file-handling middleware[3] uses Node streams by default, instead of buffering files in memory. This made it easy to use streams across our entire codebase. Besides performance, this keeps the footprint small which ensures consistent performance even for users on our smallest server configuration. [1] https://www.fastify.io/ [2] https://github.com/supabase/benchmarks [3] https://github.com/fastify/fastify-multipart

Hey everyone! We put a lot of work over the last few months into performance benchmarking. We're very keen for people to run the benchmarks themselves and report your results: https://github.com/supabase/benchmarks

Hey HN, Supabase is an open source Firebase alternative. We're building the features of Firebase using enterprise-grade open source tools. We're particularly focused on scalability. We take proven tools like Postgres, and we make them as easy to use as Firebase. Supabase had an Alpha launch [1] six months ago. This time we're more stable and feature-full. For the past 2 months we've run benchmarks [2] and security audits and we're confident to take on production workloads. Our current feature-set includes a realtime engine [3] on top of Postgres, auto-generated APIs using PostgREST [4], and Auth with Row Level Security, OAuth, and magic links [5] . We have a full dashboard, with built-in SQL Editor (full Monaco editor) and a Table View (like Airtable) [6]. Next we are focused Storage & Functions, as well as the local development experienc

Yes, we are benchmarking all of the components we use in Supabase, including the end-to-end system here: https://github.com/supabase/benchmarks/issues We still have a few benchmarks to complete, but PostgREST has been thoroughly tested now. Steve just spent the past month improving throughput on PostgREST, with amazing results (50% increase). tldr: for simple GET requests on a t3a.nano you can get up to ~2200 requests/s with db-pooling.

Hey, can you elaborate more on how you were using it and where it was failing? I'm genuinely curious as we use it at Supabase. I assume you were using it with high throughput? We are benchmarking it at around 2000 request/s now [1], and finding it's better to scale it horizontally rather than vertically. > process millions of heavy computing requests Was this reads from the database? Was the compute happening inside a Postgres function/view? [1] Benchmarks https://github.com/supabase/benchmarks/issues/2

Every project on https://supabase.io uses PostgREST. It's an amazing tool, especially when combined with Row Level Security. We have built client libraries for Javascript, Rust, Python, Dart, and a few more on the way thanks to all the community maintainers. Supabase employs the PostgREST maintainer (Steve), who is an amazing guy. He works full-time on PostgREST, and there are a few cool things coming including better JSONB and PostGIS support. We recently benchmarked PostgREST for those interested: https://github.com/supabase/benchmarks/issues/2 nb: i'm a supabase cofounder