It's a general ORM issue.

I once took a Python API with SQL Alchemy and took 30% of the speed by adding an eager load instruction to a query. Python profiling showed a lot of time in the ORM & database, then turning on SQL logging made the issue obvious.

Still feels like it should be called the "1 + N" problem tho. The 1 query happens first, then the N queries afterwards.