News for hackers. Stuff that matters.
Re:Understanding N + 1 queries problem by acjohnson55 on Monday January 02, 2023 @02:26PM (#34222434)
I can't help but feel this problem is indicative of incidental complexity in how we develop web applications. Not saying the PHP glory days were better, but there's something to be said for removing the layers of abstraction between the data and the presentation. Make the database query using SQL directly, and then inject the results into the HTML template to be delivered to the browser. Obviously, there were many issues here, like how easy it was to leave applications open to SQL injection attacks.

But it has been interesting to see the tide turn back towards server-side rendering, relying on partial DOM replacement for client-side updates. For web apps that don't have massive numbers of UI states (like a document editor), it seems like people are rethinking the wisdom thick client-side JavaScript applications, which seem to be one of the main motivators for REST API layers, and the need to efficiently fulfill N+1 queries.

Although, I do remember dealing with the N+1 problem when doing Django server-side apps more than a decade ago, before the dominance of client-side apps. I guess it was more the rise of MVC architecture and the active record pattern (https://en.wikipedia.org/wiki/Active_record_pattern) that brought the N+1 problem, more so than client-side apps.

Re:Understanding N + 1 queries problem by Arch-TK on Monday January 02, 2023 @03:17PM (#34223073)
This is specifically just a problem with all ORMs. They attempt to solve the object-relational mismatch and fail because these two concepts (sets of tuples and graphs) are completely orthogonal.
Re:Understanding N + 1 queries problem by jbverschoor on Monday January 02, 2023 @04:01PM (#34223591)
No it's not.. you can and will easily have the same problem with SQL if you're not fetching beforehand..

I bet wordpress (or many plugins) is/are so slow exactly because of this.

ORMs will even make it easier to write more efficient queries is many cases.

Re:Understanding N + 1 queries problem by Arch-TK on Monday January 02, 2023 @04:31PM (#34223939)
If you intentionally write poor code with plain SQL you will have the same problem as the auto-generated poor code of a lot of ORMs? Yes?

I don't think Wordpress is relevant here in any way. If the code is poorly written and has N+1 queries problems then it is either poorly written or is trying to half-ass an ORM.

Lastly, I would like a lot of citations to prove to me that ORMs produce more efficient queries. What produces more efficient queries in all my experience is a good understanding of relational databases, better query planners and better database design.

Re:Understanding N + 1 queries problem by hinkley on Monday January 02, 2023 @04:19PM (#34223819)
There are too many questions to make any absolute statements. You hint at a couple here.

Specialization of requests reduces data transport, but increases testing surface area and drastically reduces caching options - including within the database. Years ago we discovered that our bottleneck in Oracle was being caused by query cache evictions (worse, in 9i only queries currently in the cache could run, so new queries were blocking in the query planner. I'm not sure if this was ever fixed.)

One of the important uses of etags within your infrastructure is to allow you to incorporate data manipulation into your caches. If your functions are deterministic you can store the results of a calculation, instead of the source data for that calculation. Cache hits then don't just save bandwidth, they also save computation, which reduces the sequential parts of the response, fighting Amdahl's Law.

Re:Understanding N + 1 queries problem by chc on Monday January 02, 2023 @05:30PM (#34224594)
This was very much a problem for WordPress back in its "glory days." I had to go in and optimize a lot of stuff to get our website's performance to be sub-5s. (I haven't worked with WordPress in years, so I can't comment on its current state, but I wouldn't be surprised if this is still a thing.)
Re:Understanding N + 1 queries problem by fabian2k on Monday January 02, 2023 @04:23PM (#34223859)
This is not a problem with all ORMs. This is caused by lazy loading the related data when it is accessed, which is not how all ORMs work. If your ORM requires you to define the included related data explicitly, you won't have this particular problem.
Re:Understanding N + 1 queries problem by Arch-TK on Monday January 02, 2023 @04:32PM (#34223957)
And an ORM which eagerly loads all related data before it is accessed will have a different but related problem. I'm actually not aware of any ORM which tries to do more than trivial guessing of when data needs to be eagerly loaded. There is no easy way of solving this problem within an ORM without either causing a different problem or without leaking the abstraction a lot and requiring lots of additional complexity to annotate what you want the ORM to actually do.
Re:Understanding N + 1 queries problem by Lapsa on Tuesday January 03, 2023 @02:33AM (#34228859)
real fun begins when random Cartesian products shits up all your RAM
Re:Understanding N + 1 queries problem by fabian2k on Tuesday January 03, 2023 @02:45AM (#34228913)
In EF Core for example you have to specify which relations to include, either using ".Include()" or transforming the entire query with a "Select()". In the latter case this works pretty much automatically as long as you stay within the kinds of expressions EF Core can translate to SQL.

There is a different performance problem lurking with this design though. You have to decide whether to tell EF Core to do a query per relation or everything in one query. The single query is very efficient for many simple cases and ensures consistency, but it can fail spectacularly if you have a very large number of relations. This is a pretty significant footgun, but if you really don't want to be bothered with this you can just always use split queries.

ORMs can't really abstract over all performance considerations. They are convenient, but they can't fully hide what the database is doing under the hood.

Re:Understanding N + 1 queries problem by imtringued on Tuesday January 03, 2023 @05:14AM (#34229809)
You just specify which relations you want to load in your query. It is that simple.

There is no gotcha here.

Re:Understanding N + 1 queries problem by guggle on Tuesday January 03, 2023 @05:44AM (#34229964)
I don't know why this comment is downvoted. That's how Django ORM works too (select_related)
Re:Understanding N + 1 queries problem by Izkata on Tuesday January 03, 2023 @09:26AM (#34231693)
The abstraction leakage in Django is to know whether you should use "select_related" or "prefetch_related".
Re:Understanding N + 1 queries problem by hgsgm on Monday January 02, 2023 @04:37PM (#34224014)
Tuples are Objects Graphs are Relations.

ORM (or GTM if you like) helps you navigate your Graph of Tuples.

Re:Understanding N + 1 queries problem by Arch-TK on Monday January 02, 2023 @08:53PM (#34226537)
Sets of tuples and graphs of objects are fundamentally incompatible and I have not found a single ORM which didn't completely fail to pave over this fundamental incompatibility.

The object-relational impedance mismatch is not just something I came up with to shit on ORM. It is a well understood and widely known phenomenon which ORM users often like to insist on pretending doesn't exist. To claim that sets of tuples are the same as object graphs is like claiming that you have solved the halting problem.

Feel free to claim that the impedance mismatch is small enough that a sufficiently advanced ORM might successfully abstract it away, I don't think this claim is defensible either but on the other hand claiming that the OR impedance mismatch doesn't exist makes me think you have no idea what problem an ORM actually solves. It certainly makes me wonder how you would justify the size and complexity of every ORM out there.

Re:Understanding N + 1 queries problem by 8note on Tuesday January 03, 2023 @03:08AM (#34229066)
Isn't an adjacency list a set of 2-ples?

That's a set of tuples that defines a graph

Re:Understanding N + 1 queries problem by Arch-TK on Tuesday January 03, 2023 @05:24PM (#34239007)
Try re-creating a relational database in a graph database or vice versa by applying this approach and report back. I promise you that if you put a graph in a SQL database or vice versa you will end up with absolutely abysmal performance unless you explicitly go out of your way to special case everything into being performant.
Re:Understanding N + 1 queries problem by nightski on Tuesday January 03, 2023 @09:13AM (#34231516)
The problem isn't the mismatch of the data structures. Like at all. Imo it comes down to lazy loading and that's about it. Using lazy loading to navigate relationships is where the impedance mismatch manifests and it is completely avoidable (basically a do at your own risk, danger ahead type of scenario).
Re:Understanding N + 1 queries problem by Arch-TK on Tuesday January 03, 2023 @05:22PM (#34238989)
How is it avoidable? It's a necessary part of using an ORM. Moreover, you're severely understating the complexity of dealing with how to load data through an ORM and how to control the underlying queries.

SQL is already a perfectly adequate language for describing how to query relational data, by putting a effectively a graph query language in front of it and adding a translation layer you immediately need an immense amount of special casing, the common cases might be handled by a sufficiently sophisticated ORM but once you veer even slightly outside the realm of a basic hello world application which accesses a database you are immediately hit with a wave of all the complexity which results from the abstraction leaking. Every time I've personally dealt with an ORM or seen code which deals with an ORM, the amount of unnecessary hassle which is required just to get the ORM to do what you want it to do certainly outweighs any imagined benefit of using it. If you think SQL is hard to write then you're putting the blinders on to claim that ORMs are easier to deal with.

If you have never hit upon these sorts of issues then you must have never actually needed to do anything non-trivial and performant with an ORM.

Re:Understanding N + 1 queries problem by nightski on Tuesday January 03, 2023 @06:32PM (#34239687)
I primarily use EF, although I have used many others in the past. You are right that not all ORMs are equal, not even close.

But with EF at least those problems aren't really a big deal. You are right that SQL is perfectly adequate - great actually. I generally think in terms of SQL before loading data with a Linq query.

Often I'll do a query that projects to a model/dto. Or if I do need to load the entity and it's relations, I'll craft it just like I would in SQL. You can load the desired related entities first and then when you load the main entity they get auto populated since they are in the context. It's easy to build exactly what you need this way.

So why use an ORM? Well for one, on commands if I load an entity I get change detection for free. I get bulk inserts/updates/deletes for free (Using ef extensions). I get strongly typed queries for free. I'm able to find all references to a particular table or column across my entire code base with a single click. I can build up queries dynamically via linq. There's a lot of huge benefits that save a lot of time.

Re:Understanding N + 1 queries problem by taffer on Tuesday January 03, 2023 @04:58AM (#34229730)
The problem lies in the word navigate. The code in the article navigates through a graph. There is simply no way to navigate graphs in an eagerly evaluated language without running into the N+1 problem. A declarative language that can be lazily evaluated by the DBMS is the only way to efficiently query a graph.
Re:Understanding N + 1 queries problem by avereveard on Tuesday January 03, 2023 @05:52AM (#34230003)
proper orm allow you to specify how to process relationships, best one on a per query basis and not on a per model basis. then they aggregate the table resulting from the join presenting a deduplicated view of the root object and all the related one fetched.
Re:Understanding N + 1 queries problem by Arch-TK on Tuesday January 03, 2023 @05:26PM (#34239028)
This is a major abstraction leak and is very rarely as simple as you describe it. The only time I've seen it be this simple is with people who design their databases entirely around an ORM and in that case they're already leaving a large amount of performance on the table which you can no longer recover by reaching behind the scenes to help the ORM figure out what it needs to do.
Re:Understanding N + 1 queries problem by ramchip on Monday January 02, 2023 @03:45PM (#34223413)
I really like the compromise taken by Ecto (in Elixir): higher level than writing SQL directly, but without lazy loading, callbacks, and other features that make it difficult to see what a piece of code is really doing.
Re:Understanding N + 1 queries problem by serverholic on Monday January 02, 2023 @04:01PM (#34223592)
At my first job out of school we didn't use an ORM and just queried with raw SQL. I had never heard of the N+1 query problem because it wasn't something we really had to worry about.

After that I joined a startup that used rails and I had quite the education in ORMs and N+1 queries. The ORM felt quite restricting and I felt a lot less confident in my code.

Re:Understanding N + 1 queries problem by acdha on Monday January 02, 2023 @05:03PM (#34224299)
I saw this tons back then, too. Even back in the paleo-web you’d see people writing nested for loops, sometimes obscured by functions or a class structure but sometimes just the adjacent HTML.

As you noted, this is one of the reasons why client-side JavaScript often falls far short of the envisioned benefits. In both cases, however, I would suggest that while the trend is real and should inform your architecture the most important thing is to routinely use your monitoring. Different apps have different performance challenges but they all need to be observable and I’ve seen so many times where people wasted tons of time and resources shooting in the dark because they didn’t have granular monitoring or thought it was too hard.

One of the best example I had was a while back when I inherited a Django codebase which was too slow. One of the developers had spent a couple days rewriting everything in Jinja2 because “Django is slow”, introducing the bugs you’d expect and leading to lots of new custom code to maintain (such as 3 versions of the human size formatting function). Performance didn’t budge. Six months later, I saw the MySQL query counter spiraling up on every page view, installed Django Debug Toolbar, looked at the queries, and spent an afternoon reverting all of the templates and fixing the N+1 queries which had always been the problem. That was tens of thousands of lines of code churn all wasted for what was eventually maybe 50 lines changed against the original codebase.

One thing I introduced which worked well was a test hook which failed based on the query counts for a view. That caught most N+1 issues and is conveniently easy to implement with almost any model.

Re:Understanding N + 1 queries problem by mireq2 on Tuesday January 03, 2023 @09:56AM (#34232123)
I spent couple days rewriting everything from Django to Jinja2 and it was really big difference with 10x speedup (from 500ms for invoice list to 50ms). It was big e-commerce system with every ORM query optimized, selecting only required fields, prefetching related relations or selecting related. Django templates are really really slow and hard to debug. Rewrite was really great decision in this case.
Re:Understanding N + 1 queries problem by acdha on Tuesday January 03, 2023 @11:20AM (#34233438)
I’ve never seen a difference that pronounced (I’m guessing that you had a lot of template logic?) but that sounds like you did it the right way: based on profiling.
Re:Understanding N + 1 queries problem by pmontra on Tuesday January 03, 2023 @02:53AM (#34228962)
> Make the database query using SQL directly, and then inject the results into the HTML template to be delivered to the browser.

This is what I do for the most complex queries, where translating them to the ORM would be a time consuming pain. What I do normally is think in SQL and write in the ORM language. After all the API of the database is SQL, not the ORM, and I already know SQL.

In this way it's obvious that you have to write includes(:comments), because it's a join, and it's obvious that the original

  object.votes.count
would generate one query each time it is called. I write the separate queries and compose the results instead. I'm not using BatchLoader or other gems. Using directly the ORM is enough.

If this query turns out to be important for the performances of the application, I'll think about a way to write it with a single query in SQL to make the database do all the work. Then translate it in ActiveRecord or leave it in SQL if it takes too long. Sometimes it's not obvious how to do it, a problem common to all ORMs of all languages.

Edit: somebody called saila gave an example of such a query in the comments one hour before I wrote my reply.

Re:Understanding N + 1 queries problem by imtringued on Tuesday January 03, 2023 @05:36AM (#34229923)
A lot of complex computed properties can easily be made efficient by having "WITH" statements.

The with query starts with the ID of the object to which the computed property is attached to. So in this case you would do the same thing as the author and write

WITH comment_vote_count as select comment_id, COUNT(vote_id) from comment left join vote;

The ORM would just treat this like a normal table and do a join based on the comment ID except the ORM provides a convenient API to do this, which it currently does not...

Re:Understanding N + 1 queries problem by brightball on Tuesday January 03, 2023 @08:52AM (#34231275)
There's a Ruby gem called Bullet that identifies and warns developers about N+1 problems. You can also have it fail tests if detected.

I don't know if the approach is possible with every ORM or if it's just leveraging some Ruby perks, but I can't think of a good reason why you wouldn't use the equivalent everywhere.

https://github.com/flyerhzm/bullet