Eloquent Performance: 4 Examples of N+1 Query Problems

Eloquent performance is typically the main reason for slow Laravel projects. A big part of that is a so-called “N+1 Query Problem”. In this article, I will show a few different examples of what to watch out for, including the cases when the problem is “hidden” in unexpected places in the code.

What is the N+1 Query Problem

In short, it’s when Laravel code runs too many database queries. It happens because Eloquent allows developers to write a readable syntax with models, without digging deeper into what “magic” is happening under the hood.

This is not only an Eloquent, or even Laravel, problem: it’s well-known in the dev industry. Why is it called “N+1”? Because, in the Eloquent case, it queries ONE row from the database, and then performs one more query for EACH related record. So, N queries, plus the record itself, total N+1.

To solve it, we need to query the related records upfront, and Eloquent allows us to do that easily, with so-called eager loading. But before we get to the solutions, let’s discuss the problems. I will show you 4 different cases.

Case 1. “Regular” N+1 Query.

This one can be taken directly from the official Laravel documentation:

1// app/Models/Book.php:

2class Book extends Model


4 public function author()

5 {

6 return $this->belongsTo(Author::class);

7 }



10// Then, in some Controller:

11$books = Book::all();


13foreach ($books as $book) {

14 echo $book->author->name;


What happens here? The $book->author part will perform one extra DB query for every book, to get its author.

I’ve created a small demo project to simulate this and seeded 20 fake books with their authors. Look at the number of queries.

N+1 Query Example 1 - No Eager Loading

As you can see, for 20 books, there are 21 queries, exactly N+1, where N = 20.

And yes, you get it right: if you have 100 books on the list, you will have 101 queries to the DB. Awful performance, although the code seemed “innocent”, right.

The fix is to load the relationship upfront, immediately in the Controller, with the eager loading that I mentioned earlier:

1// Instead of:

2$books = Book::all();


4// You should do:

5$books = Book::with('author')->get();

The result is much better – only 2 queries:

N+1 Query Example 1 - Eager Loading

When you use eager loading, Eloquent gets all the records into the array and launches ONE query to the related DB table, passing those IDs from that array. And then, whenever you call $book->author, it loads the result from the variable that is already in memory, no need to query the database again.

Now, wait, you wonder what is this tool to show queries?

Always Use Debugbar. And Seed Fake Data.

This bottom bar is a package Laravel Debugbar. All you need to do to use it is install it:

1composer require barryvdh/laravel-debugbar --dev

And that’s it, it will show the bottom bar on all the pages. You just need to enable debugging with the .env variable APP_DEBUG=true, which is a default value for local environments.

Security Notice: make sure that when your project goes live, you have APP_DEBUG=false on that server, otherwise regular users of your website will see the debugbar and your database queries, which is a huge security issue.

Of course, I advise you to use Laravel Debugbar on all your projects. But this tool by itself will not show the obvious problems until you have more data on the pages. So, using Debugbar is only one part of the advice.

In addition, I also recommend having seeder classes that would generate some fake data. Preferably, a lot of data, so you would see how your project performs “in real life” if you imagine it growing successfully in the future months or years.

Use Factory classes and then generate 10,000+ records for books/authors and other models:

1class BookSeeder extends Seeder


3 public function run()

4 {

5 Book::factory(10000)->create();

6 }


Then, browse through the website and look at what Debugbar shows you.

There are also other alternatives to Laravel Debugbar:

Case 2. Two Important Symbols.

Let’s say that you have the same hasMany relationship between authors and books, and you need to list the authors with the number of books for each of them.

Controller code could be:

1public function index()


3 $authors = Author::with('books')->get();


5 return view('authors.index', compact('authors'));


And then, in the Blade file, you do a foreach loop for the table:

1@foreach($authors as $author)

2 <tr>

3 <td>{{ $author->name }}</td>

4 <td>{{ $author->books()->count() }}</td>

5 </tr>


Looks legit, right? And it works. But look at the Debugbar data below.

N+1 Query Example 2 - Bad Performance

But wait, you would say that we are using eager loading, Author::with('books'), so why there are so many queries happening?

Because, in Blade, $author->books()->count() doesn’t actually load that relationship from the memory.

  • $author->books() means the METHOD of relation
  • $author->books means the DATA eager loaded into memory

So, the method of relation would query the database for each author. But if you load the data, without () symbols, it will successfully use the eager loaded data:

N+1 Query Example 2 - Good Performance

So, watch out for what you’re exactly using – the relationship method or the data.

Notice that in this particular example there’s an even better solution. If you need only the calculated aggregated data of the relationship, without the full models, then you should load only the aggregates, like withCount:

1// Controller:

2$authors = Author::withCount('books')->get();


4// Blade:

5{{ $author->books_count }}

N+1 Query Example 2 - Best Performance

As a result, there will be only ONE query to the database, not even two queries. And also the memory will not be “polluted” with relationship data, so some RAM saved as well.

Case 3. “Hidden” Relationship in Accessor.

Let’s take a similar example: a list of authors, with the column of whether the author is active: “Yes” or “No”. That activity is defined by whether the author has at least one book, and it is calculated as an accessor inside of the Author model.

Controller code could be:

1public function index()


3 $authors = Author::all();


5 return view('authors.index', compact('authors'));


Blade file:

1@foreach($authors as $author)

2 <tr>

3 <td>{{ $author->name }}</td>

4 <td>{{ $author->is_active ? 'Yes' : 'No' }}</td>

5 </tr>


That “is_active” is defined in the Eloquent model:

1use Illuminate\Database\Eloquent\Casts\Attribute;


3class Author extends Model


5 public function isActive(): Attribute

6 {

7 return Attribute::make(

8 get: fn () => $this->books->count() > 0,

9 );

10 }


Notice: this is a new syntax of Laravel accessors, adopted in Laravel 9. You can also use the “older” syntax of defining the method getIsActiveAttribute(), it will also work in the latest Laravel version.

So, we have the list of authors loaded, and again, look what Debugbar shows:

N+1 Query Example 3 - Bad Performance

Yes, we can solve it by eager loading the books in the Controller. But in this case, my overall advice is avoid using relationships in accessors. Because an accessor is usually used when showing the data, and in the future, someone else may use this accessor in some other Blade file, and you will not be in control of what that Controller looks like.

In other words, Accessor is supposed to be a reusable method for formatting data, so you’re not in control of when/how it will be reused. In your current case, you may avoid the N+1 query, but in the future, someone else may not think about it.

Case 4. Be Careful with Packages.

Laravel has a great ecosystem of packages, but sometimes it’s dangerous to use their features “blindly”. You can run into unexpected N+1 queries if you’re not careful.

Let me show you an example with a very popular spatie/laravel-medialibrary package. Don’t get me wrong: the package itself is awesome and I don’t want to show it as a flaw in the package, but rather as an example of how important it is to debug what is happening under the hood.

Laravel-medialibrary package uses polymorphic relationships between the “media” DB table and your model. In our case, it will be books that will be listed with their covers.

Book model:

1use Spatie\MediaLibrary\HasMedia;

2use Spatie\MediaLibrary\InteractsWithMedia;


4class Book extends Model implements HasMedia


6 use HasFactory, InteractsWithMedia;


8 // ...


Controller code:

1public function index()


3 $books = Book::all();


5 return view('books.index', compact('books'));


Blade code:

1@foreach($books as $book)

2 <tr>

3 <td>

4 {{ $book->title }}

5 </td>

6 <td>

7 <img src="{{ $book->getFirstMediaUrl() }}" />

8 </td>

9 </tr>


That getFirstMediaUrl() method comes from the official documentation of the package.

Now, if we load the page and look at the Debugbar…

N+1 Query Example 4 - Bad Performance

20 books, 21 queries to the database. Precisely N+1 again.

So, the package does a bad job in performance? Well, no, because the official documentation is telling how to retrieve media files for one specific model object, for one book, but not for the list. That list part you need to figure out by yourself.

If we dig a bit deeper, in the trait InteractsWithMedia of the package, we find this relationship that is auto-included in all models:

1public function media(): MorphMany


3 return $this->morphMany(config('media-library.media_model'), 'model');


So, if we want all the media files to be eager loaded with the books, we need to add with() to our Controller:

1// Instead of:

2$books = Book::all();


4// You should do:

5$books = Book::with('media')->get();

This is the visual result, only 2 queries.

N+1 Query Example 4 - Good Performance

Again, this is the example not to show this package as a bad one, but with the advice that you need to check the DB queries at all times, whether they come from your code or an external package.

The Built-In Solution Against N+1 Query

Now, after we’ve covered all 4 examples, I will give you the last tip: since Laravel 8.43, the framework has a built-in N+1 Query detector!

In addition to the Laravel Debugbar for inspection, you can add a code to the prevention of this problem.

You need to add two lines of code to app/Providers/AppServiceProvider.php:

1use Illuminate\Database\Eloquent\Model;


3class AppServiceProvider extends ServiceProvider


5 public function boot()

6 {

7 Model::preventLazyLoading(! app()->isProduction());

8 }


Now, if you launch any page that contains an N+1 Query problem, you will see an error page, something like this:

N+1 Query - Prevent Lazy Loading

This will show you the exact “dangerous” code that you may want to fix and optimize.

Note that this code should be executed only on your local machine or testing/staging servers, live users on production servers should not see this message, cause that would be a security issue. That’s why you need to add a condition like ! app()->isProduction(), which means that your APP_ENV value in the .env file is not “production”.

Interestingly, this prevention didn’t work for me when trying with the last example of Media Library. Not sure if it’s because it comes from the external package, or because of polymorphic relations. So, my ultimate advice still stands: use Laravel Debugbar to monitor the number of queries and optimize accordingly.

You can find all 4 examples in the free repository on Github and play around with them.

Wish you have a great speed performance in your projects!

Source link


Leave a Reply

Your email address will not be published. Required fields are marked *