ok so say your ORM-backed endpoint is fine locally and slow in production. The query log shows the same SELECT ... WHERE id = ? repeated hundreds of times per request.
locally everything feels instant cuz the test database is tiny, so nobody noticed until real data arrived. throwing a bigger database server at it seems like teh wrong answer.
Whats the standard way to fix this, and how do you stop it from creeping back in?
lol same thing happened to me node with an ORM on top of PostgreSQL. no pagination currently; teh frontend loads everything and paginates on teh client. the response is a few MB now.
ahh classic to stop it creeping back, make it visible. Log teh number of queries per request in development and fail a test if an endpoint exceeds a threshold. Some ORMs and frameworks have pulgins that warn about lazy loading inside loops. Catching it in code review is much cheaper than in production. worked for me anyway 🤷
happy to help with this one. @farah_patch eager loading everything isn't free either. Joining several one-to-many relations in one query can multiply rows and pull far more data than needed. Sometimes two or three separate queries (load posts, then load all authors with WHERE id IN (...)) beat one giant join. Measure both instead of assuming the single query wins.
hmm idk idk man that sounds like bad advice tbh idk maybe im wrong lol
been there man for me it was teh settings. swapped it and boom, fixed
how is this trhead still going lmao
hmmm for me it was the cable. swapped it and boom, fixed lmk how it goes
hmmm for me it was the cable. swapped it and boom, fixed lmk how it goes
lol no
Sign in or create an account to reply.
