Benchmark Supabase (fly.io) · Issue #6 · supabase/benchmarks · GitHub
Skip to content

Benchmark Supabase (fly.io) #6

Open

Description

@kiwicopple

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

image

Write benchmarks

image

Activity

  1. kiwicopple commented on Nov 20, 2020

    @kiwicopple
    MemberAuthor

    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

    image

    Write

    image

  2. kiwicopple commented on Nov 20, 2020

    @kiwicopple
    MemberAuthor

    TLDR

    Setup:

    • AWS: t3a.micro (Kong -> Postgres) -> database (EC2 t3a.micro)
    • Fly: (Postgres) -> database (EC2 t3a.micro)

    Read

    • AWS: 303/s
    • Fly: 206/s

    Write

    • AWS 307/s
    • Fly: 277/s

    Notes

    • Running from my local machine, so latency included
    • AWS is going through cloudflare (DNS only), and then Kong, then Postgrest.
    • Strange that read is slower than write (?)
    • All systems deployed in Singapore
  3. awalias commented on Nov 22, 2020

    @awalias
    Member

    why is your AWS run so much slower than my results

  4. kiwicopple commented on Nov 22, 2020

    @kiwicopple
    MemberAuthor

    I was wondering the same actually. I just ran this code against our Benchmarks project. Is that how you did it?

  5. kiwicopple commented on Nov 24, 2020

    @kiwicopple
    MemberAuthor

    Benchmarks on Fly micro 1x: not a huge difference in throughput, but it did result in some duration thresholds to drop out

    image

    image

  6. kiwicopple commented on Nov 24, 2020

    @kiwicopple
    MemberAuthor

    I'll add a comparison table to the top comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions