Laravel Performance

Sign in Get started

This episode is for members only

Sign up to access "Laravel Performance" right now.

Already a member? Sign in to continue

Playing

06. Pagination

Episodes

0%

Your progress

Total: 1h 9m
Played: 0m
Remaining: 1h 9m

Join or sign in to track your progress

01. Introduction

02. Setting up the example project

03. Using debugbar

04. Eager loading

05. Forcing eager loading

07. Pull back only the columns you need

08. Selecting columns on related models

09. Adding database indexes

10. Fetching counts efficiently

11. Caching basics

12. Clearing cached data by tags

13. Chunking with Eloquent

14. Queuing emails

15. Mass deleting

Transcript

00:00

So this one might seem pretty obvious, but over on the homepage at the moment, we are just iterating through all of our posts, we're not actually paginating anything.

00:09

And it's really important to consider pagination, particularly when you start a project and you start iterating through stuff, but you have no idea that in the future, things might get a little bit longer than you expect. Now, luckily in Laravel, pagination is very, very easy to do.

00:23

So we're going to go over and just start to paginate this data, keeping an eye on not the query count, because it's going to be the same or roughly the same, because we might not have as many users included in that first pagination set, but also the memory usage as well. And of course, the request duration for our app.

00:42

Okay, so we're going to head over to the home controller, and we're going to switch get out to paginate. And we're going to choose a sensible amount of records that we want to display per page. Now, when we come over, what we should see here is the amount of users being pulled in reduced, we'll see the memory usage go down,

00:58

and we should see the request duration go down as well. So you can see here that we have a additional query, but that's fine. That's just part of the pagination, selecting the amount of posts that we currently have. But you can see the memory usage has gone down dramatically here.

01:13

The request duration has gone down as well. And of course, on the client side, this is going to just generally be faster in the browser, because we have less data being rendered out to the page. So of course, we need some pagination links. So let's head over to the homepage here.

01:29

And just outside of this for each, we can go ahead and say posts and links. And we're pretty much done. What we should now see is some pagination down here that we can click through and see page equals three, whatever page we've clicked on. So obviously, really, really straightforward, you may have implemented pagination before.

01:52

But the reason I bring this up is it's really easy to output a list of data with your dummy data that you're working with locally. But then when your app gets pushed to production, and you have a huge amount of data flow in like posts or comments,

02:05

you're going to end up seeing a massive delay in your page load speed, because that's something you can't control. With pagination, at least you can control what is displayed per page. So you have a very good idea of the speed of your app.

Episode summary

In this episode, we take a practical look at implementing pagination on the homepage of our Laravel app. Right now, we’re just loading all of our posts at once—which works fine with a small dataset, but as your app grows (hello, production!), this can seriously slow things down.

We start by heading to the HomeController and swapping out our basic get for the magic of paginate, choosing a sensible number of posts per page. Right away, we see the number of users pulled in goes down, memory usage drops, and overall request duration shrinks. These are wins both for your server and your user experience.

We then add the built-in pagination links in the view, so your users can easily click through the different pages of posts. It’s super straightforward in Laravel, but so easy to forget when you’re developing locally with only a handful of dummy records!

Finally, we discuss why this matters: in real-world scenarios, unpaginated lists can cripple your app’s performance as your dataset grows. Pagination puts you back in control, ensuring your page loads stay snappy no matter how much content you’ve got.

So, by the end of this lesson, you’ll have a nicely paginated posts list, and you’ll know exactly why it’s important—not just for keeping things neat, but for keeping your app fast.

Episode discussion

No comments, yet. Be the first!