Seeding data in Laravel - Performance & Optimization

Performance: Seeding data

MEDIUM IMPACT

Seeding data affects initial database setup speed and can impact server response time during development or testing.

Populating database with initial test or demo data

Laravel

<?php
use Illuminate\Database\Seeder;
use Illuminate\Support\Facades\DB;

class DatabaseSeeder extends Seeder {
    public function run() {
        $users = [];
        for ($i = 0; $i < 10000; $i++) {
            $users[] = [
                'name' => 'User ' . $i,
                'email' => 'user' . $i . '@example.com',
                'password' => bcrypt('password'),
            ];
        }
        DB::table('users')->insert($users);
    }
}

Inserts all records in a single batch reducing database calls and speeding up seeding.

📈 Performance GainSingle database insert operation instead of 10,000, reducing execution time drastically.

Populating database with initial test or demo data

Laravel

<?php
use Illuminate\Database\Seeder;
use Illuminate\Support\Facades\DB;

class DatabaseSeeder extends Seeder {
    public function run() {
        for ($i = 0; $i < 10000; $i++) {
            DB::table('users')->insert([
                'name' => 'User ' . $i,
                'email' => 'user' . $i . '@example.com',
                'password' => bcrypt('password'),
            ]);
        }
    }
}

Inserts each record one by one causing many database calls and slow execution.

📉 Performance CostTriggers 10,000 separate database insert operations, blocking execution for seconds or more.

Performance Comparison

Pattern	Database Calls	Execution Time	Server Load	Verdict
Single inserts in loop	10,000 calls	High	High	[X] Bad
Batch insert all records	1 call	Low	Low	[OK] Good

Rendering Pipeline

Seeding data runs on the server side before page rendering, so it does not directly affect browser rendering but impacts backend response time and server load.

→Server Processing

→Database I/O

⚠️ BottleneckDatabase insert operations

Optimization Tips

1Avoid inserting records one by one in loops during seeding.

2Use batch inserts to minimize database calls and speed up seeding.

3Monitor database query count and execution time to optimize seeding performance.

Performance Quiz - 3 Questions

What is the main performance issue with inserting records one by one in a seeder?

A It triggers multiple CSS reflows

B It causes many database calls increasing execution time

C It uses too much memory on the client browser

D It blocks JavaScript event loop

DevTools: Network (server timing) and Laravel Telescope

How to check: Use Laravel Telescope or server logs to monitor database query count and duration during seeding; check server response time in Network panel.

What to look for: Look for high number of queries or long execution times indicating inefficient seeding.

Practice

1. What is the main purpose of a seeder in Laravel?

easy

A. To fill the database with sample or default data automatically

B. To create database tables and columns

C. To handle user authentication

D. To manage application routes

Solution

1. Step 1: Understand the role of seeders

   Seeders are designed to insert data into the database automatically for testing or initial setup.

2. Step 2: Differentiate from other Laravel features

   Creating tables is done by migrations, authentication by middleware, and routes by route files, not seeders.

3. Final Answer:

   To fill the database with sample or default data automatically -> Option A

4. Quick Check:

   Seeder purpose = fill database with data [OK]

Hint: Seeders add data, migrations create tables [OK]

Common Mistakes:

• Confusing seeders with migrations
• Thinking seeders manage routes
• Assuming seeders handle authentication

2. Which command creates a new seeder class in Laravel?

easy

A. php artisan make:seeder SeederName

B. php artisan create:seeder SeederName

C. php artisan seed:create SeederName

D. php artisan generate:seeder SeederName

Solution

1. Step 1: Recall Laravel artisan commands for seeders

   The correct command to create a seeder is php artisan make:seeder SeederName.

2. Step 2: Identify incorrect command formats

   Other options use wrong verbs like create, seed:create, or generate which are not valid artisan commands.

3. Final Answer:

   php artisan make:seeder SeederName -> Option A

4. Quick Check:

   Seeder creation command = make:seeder [OK]

Hint: Use 'make:seeder' to create seeders [OK]

Common Mistakes:

• Using 'create:seeder' instead of 'make:seeder'
• Confusing seeder creation with migration creation
• Typing artisan commands with wrong verbs

3. Given this seeder code snippet, what will be the result after running php artisan db:seed --class=UserSeeder?

public function run() {
  DB::table('users')->insert([
    ['name' => 'Alice', 'email' => '[e-mail]'],
    ['name' => 'Bob', 'email' => '[e-mail]']
  ]);
}

medium

A. Only one user will be added because insert accepts one record at a time

B. The users table will be emptied before adding Alice and Bob

C. An error will occur because the insert method requires a single array

D. Two new users named Alice and Bob will be added to the users table

Solution

1. Step 1: Understand DB insert with array of arrays

   Passing an array of arrays to insert adds multiple records at once.

2. Step 2: Confirm no truncation or errors in code

   The code inserts two users without deleting existing data, and the syntax is correct.

3. Final Answer:

   Two new users named Alice and Bob will be added to the users table -> Option D

4. Quick Check:

   Insert multiple records = array of arrays [OK]

Hint: Insert accepts array of arrays for multiple rows [OK]

Common Mistakes:

• Assuming insert deletes existing data
• Thinking insert only accepts one record
• Expecting an error from multiple inserts

4. What is wrong with this seeder code?

public function run() {
  DB::table('products')->insert(
    ['name' => 'Book', 'price' => 10],
    ['name' => 'Pen', 'price' => 2]
  );
}

medium

A. The run method must return a value

B. The table name 'products' is invalid and causes an error

C. The insert method expects a single array, but two arrays are passed separately

D. The price values must be strings, not integers

Solution

1. Step 1: Check insert method parameter format

   The insert method expects one array argument. Passing two separate arrays causes a syntax error.

2. Step 2: Identify correct way to insert multiple rows

   Multiple rows should be inside a single array: an array of arrays.

3. Final Answer:

   The insert method expects a single array, but two arrays are passed separately -> Option C

4. Quick Check:

   Insert needs one array argument [OK]

Hint: Wrap multiple records in one array for insert [OK]

Common Mistakes:

• Passing multiple arrays as separate arguments
• Thinking run method must return a value
• Assuming numeric values must be strings

5. You want to seed your database with 100 users having random names and emails using Laravel factories inside a seeder. Which code snippet correctly achieves this inside the run method?

hard

A. factory(User::class, 100)->make();

B. User::factory()->count(100)->create();

C. User::create()->factory()->count(100);

D. User::factory(100)->make();

Solution

1. Step 1: Recall Laravel factory syntax for creating multiple records

   The correct syntax is User::factory()->count(100)->create(); to generate and save 100 users.

2. Step 2: Identify incorrect factory usages

   User::create()->factory()->count(100); reverses method order, A uses old syntax, and D misses count method.

3. Final Answer:

   User::factory()->count(100)->create(); -> Option B

4. Quick Check:

   Factory count then create = correct [OK]

Hint: Use factory()->count(n)->create() to seed multiple records [OK]

Common Mistakes:

• Using old factory syntax
• Calling factory on create() result
• Omitting count() method for multiple records