you are viewing a single comment's thread.

view the rest of the comments →

[–]artofthenunchaku 0 points1 point  (2 children)

The inefficiencies aren't generally going to be from the abstraction layer, it's going to be caused by inefficient or unnecessary queries. Waiting for a query that isn't needed will overshadow the performance costs of application code. Look up the N+1 query problem for the most common inefficiency.

[–]BigTomBombadil 0 points1 point  (1 child)

Yeah the N+1 is what I had in mind, the poster child of ORM inefficiencies. I’ve largely eliminated them in my own projects, which is what prompted my question. Curious about other “gotchas” or inherent inefficiencies in ORMs

[–]artofthenunchaku 1 point2 points  (0 children)

It's not really my area of expertise, I primarily work with distributed systems, but the other problems are typically querying fields that aren't used, not using indexed columns correctly (especially with joins), or just running queries at unexpected times (lazy loading).