# Chore - Running Database on Supabase - Attached PostgREST directly to the Supabase database - Running benchmarks directly to the PostgREST (no kong) ### Results | Instance | vCPU | RAM | Price | Read | Write | Comments | |---------------|--------|-------|-------|-------|-------|-----------------------------| | AWS t3a.micro | 2 | 1 | $6.80 | 303/s | 307/s | | | Fly micro-1x | shared | 128MB | $2.67 | 171/s | 235/s | Reached request duration threshold | | Fly micro-2x | shared | 512MB | $8 | 206/s | 277/s | | ### Fly config ``` app = "postgrest" [build] image = "postgrest/postgrest" [[services]] internal_port = 3000 protocol = "tcp" [services.concurrency] hard_limit = 25 soft_limit = 20 [[services.ports]] handlers = ["http"] port = "80" [[services.ports]] handlers = ["tls", "http"] port = "443" [[services.tcp_checks]] interval = 10000 timeout = 2000 ``` ### Read benchmarks  ### Write benchmarks 
Activity
kiwicopple commentedon Nov 20, 2020
Just to make sure I am running with the same amount of data in the benchmark database, and on the same hardware, here is my run for Supabase:
Read
Write
kiwicopple commentedon Nov 20, 2020
TLDR
Setup:
Read
303/s206/sWrite
307/s277/sNotes
awalias commentedon Nov 22, 2020
why is your AWS run so much slower than my results
kiwicopple commentedon Nov 22, 2020
I was wondering the same actually. I just ran this code against our
Benchmarksproject. Is that how you did it?kiwicopple commentedon Nov 24, 2020
Benchmarks on Fly micro 1x: not a huge difference in throughput, but it did result in some duration thresholds to drop out
kiwicopple commentedon Nov 24, 2020
I'll add a comparison table to the top comment