Menu

Post image 1
Post image 2
Post image 3
1 / 3
0

How Shared GraphQL Fragments Silently Killed Our List Performance

DEV Community: graphql·Ryo Tsugawa·3 days ago
#Sgnzec3W
Reading 0:00
15s threshold

Something felt slow Our product backlog list page was sluggish. Not dramatically broken — just… off. The kind of slowness you notice when you switch from a fresh demo tenant to a real one with actual data. So I measured it: 8 items : 206ms TTFB (Time To First Byte) 67 items : 675ms TTFB That's a +469ms difference , or roughly 8ms per item of linear degradation. Every single backlog item added ~8ms to the response time. Not great. The first instinct was to blame the frontend — maybe the component tree was re-rendering too aggressively. But TTFB ruled that out immediately. The browser hadn't even started rendering; the server was taking that long to respond. So the bottleneck was somewhere between the API server and the database. Time to dig deeper. How our preloading works We run Go + gqlgen + GORM on Cloud Run, talking to Cloud SQL (MySQL). The GraphQL layer is designed around a simple principle: The client requests only the fields it needs. The server preloads only what's requested.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Read More