Chunk

Basically it will grab all the records from the DB but load 100 records in the memory. It's kind of limit and offset in pagination.

You better read the chunk part here. http://laravel-school.com/posts/laravel-pagination-vs-chunk-51

Okay, the code that I write, supposing that I put it in the view.

echo $user;

What will be printed?

whatever is in $user ????

(but only if it is a string obviously)

I mean 100 or 1000 rows? Suppose that table users has 1000 rows.

DB::table('users')->orderBy('id')->chunk(100, function ($users) {
    foreach ($users as $user) {
        //
    echo $user;
    }
});

In the documentation you have linked yourself:

If you need to work with thousands of database records, consider using the chunk method. This method retrieves a small chunk of the results at a time and feeds each chunk into a Closure for processing. This method is very useful for writing Artisan commands that process thousands of records. For example, let's work with the entire users table in chunks of 100 records at a time:

https://laravel.com/docs/6.x/queries#chunking-results

It will print 1000 rows, but it will do so executing 10 database queries (fetching 100 rows, printing them, fetching the next 100 rows, printing them etc).

get 100, loop over 100, get next 100, loop over 100 etc etc until all the records have been output

So it's row 1 - 100 ?

NO

I ask you to 100 tins of food from the shop, but you can only carry 10, so you fetch 10 then go back and get another 10, then another 10 until I have the 100

The request was for 100 tins (total records) but you could only carry 10 at a time (memory restriction)

So it's row 1 - 100 ?

• First pass ========== row 1 - 100
• second pass ========== row 101 - 200
• third pass ========== row 201 - 300

Of course "chunk" is also covered in the docs.