N+1?

Do you mean the 3N+1 problem?

Najdorf:
N+1?

Do you mean the 3N+1 problem?

I mean the N + 1 problem in SQL that causes a query to query other queries unnecessarily.

Karleb:


I mean the N + 1 problem in SQL that causes a query to query other queries unnecessarily.

It happens when you have a parent child relationship. You query the db for an object and that objects generate another query for it's children and another for the children's relationship and another e.t.c

This happens often when you are using ORM for your database interactions, and it can be mitigated by the JOIN statement. Django's ORM provides the select_related function (it uses JOIN underneath) to avoid this problem.

I dont have a full structured explanation for you but this problem is very common with GraphQL APIs. Especially when having a deep nested schema.

Its happens when you have a recursive SQL query. So one way to mitigate it is being doing a depth limit ( when using GraphQL ).

Facebook built Dataloader which batches the query and transforms it into a single SQL operation.

Sad part of this problem is that its not very noticeable except when using youre using a 3rd party logging service to log out your application queries.

if you really want to understand it I'd advise you search for it within a GraphQL API context. Since its a common problem there, they're many articles on it

cc Pcguru1

I like these responses.