Post

So this screen in @onlineornot.com has always been slower than I wanted - around 2.3s(!) to load 10 rows of data from the GraphQL endpoint. It was the first screen I ever built (4+ yrs ago), and I leaned heavily into GraphQL resolvers because I assumed it'd be fast.

11/6/25, 7:33 am0 reposts7 likes

Andri Óskarsson

@andri.dk

11 June 2025

How much latency is there between backend and db?

Max Rozen

@rozenmd.com

11 June 2025

they're both in us-east-1, should be 20ish ms at most

Andri Óskarsson

@andri.dk

11 June 2025

I mean with the query as well

Andri Óskarsson

@andri.dk

12 June 2025

Sorry for the short response, wrote it in the car 😀 I was just wondering what the cost of round-trip w. GraphQL was, compared to server-rendering the entire response.

Max Rozen

@rozenmd.com

11 June 2025

I've managed to speed it up by ~80% with one simple trick: stop relying on GraphQL. Instead of fetching data resolver-by-resolver, now I fetch all of the data in one chonker of an SQL query.

Max Rozen

@rozenmd.com

11 June 2025

Next step: move the dashboard over to the existing public REST API. Historically it's been hard to dogfood the public REST API since the whole dash uses GraphQL, so looking forward to that changing.

Andy Ingram

@andrewingram.bsky.social

11 June 2025

I’m curious as to why it’s so slow with GraphQL, as anything you can do to optimise REST you can also do with GraphQL — except for a few things like field typechecking.