One-to-many (hasMany) in Laravel - Performance & Optimization

Performance: One-to-many (hasMany)

MEDIUM IMPACT

This affects how many database queries are run and how much data is loaded into memory, impacting page load speed and responsiveness.

Loading a model with many related child models

Laravel

<?php
$posts = App\Models\Post::with('comments')->get();
foreach ($posts as $post) {
    echo $post->comments->count();
}

Eager loading fetches all comments in one query, reducing database calls.

📈 Performance GainSingle query for all related comments, reducing queries from N+1 to 2.

Loading a model with many related child models

Laravel

<?php
$posts = App\Models\Post::all();
foreach ($posts as $post) {
    echo $post->comments->count();
}

This triggers a separate database query for each post to load comments (N+1 query problem).

📉 Performance CostTriggers N+1 queries, causing slow page load and high database load.

Performance Comparison

Pattern	Database Queries	Memory Usage	Response Time	Verdict
Lazy loading (N+1 queries)	N+1 queries	Higher due to repeated loads	Slower with many related items	[X] Bad
Eager loading (with)	2 queries	Lower and predictable	Faster and scalable	[OK] Good

Rendering Pipeline

The database queries run before rendering. Multiple queries increase server response time, delaying HTML delivery and LCP.

→Data Fetching

→Server Response

→HTML Rendering

⚠️ BottleneckDatabase query count and response time

Core Web Vital Affected

LCP

This affects how many database queries are run and how much data is loaded into memory, impacting page load speed and responsiveness.

Optimization Tips

1Avoid lazy loading in loops to prevent N+1 query problems.

2Use eager loading (with) to batch fetch related models efficiently.

3Monitor database query count to keep server response fast.

Performance Quiz - 3 Questions

What is the main performance problem with lazy loading related models in a one-to-many relationship?

A It caches data too aggressively, causing stale content.

B It triggers many small database queries, slowing down page load.

C It loads all data in one big query, causing memory issues.

D It blocks rendering with heavy CSS styles.

DevTools: Network

How to check: Open DevTools, go to Network tab, filter XHR requests, and count the number of API/database calls triggered when loading the page.

What to look for: Multiple repeated queries for related data indicate N+1 problem; fewer grouped queries indicate good eager loading.

Practice

1. What does the hasMany relationship represent in Laravel?

easy

A. One model has many related models

B. Many models belong to one model

C. One model belongs to one other model

D. Many models have many related models

Solution

1. Step 1: Understand relationship types

   Laravel defines relationships to connect models. hasMany means one model owns many related models.

2. Step 2: Match relationship to description

   hasMany is used when one record relates to multiple records in another table.

3. Final Answer:

   One model has many related models -> Option A

4. Quick Check:

   hasMany = one-to-many [OK]

Hint: hasMany means one owns many others [OK]

Common Mistakes:

• Confusing hasMany with belongsTo
• Thinking hasMany means many-to-many
• Mixing up owner and owned models

2. Which of the following is the correct way to define a hasMany relationship in a Laravel model?

easy

A. public function comments() { return $this->belongsTo(Comment::class); }

B. public function comments() { return $this->hasMany(Comment::class); }

C. public function comments() { return $this->hasOne(Comment::class); }

D. public function comments() { return $this->belongsToMany(Comment::class); }

Solution

1. Step 1: Identify correct method for one-to-many

   In Laravel, hasMany() defines one-to-many relations.

2. Step 2: Match method to code

   public function comments() { return $this->hasMany(Comment::class); } uses hasMany(Comment::class), which is correct syntax.

3. Final Answer:

   public function comments() { return $this->hasMany(Comment::class); } -> Option B

4. Quick Check:

   hasMany() method syntax = public function comments() { return $this->hasMany(Comment::class); } [OK]

Hint: Use hasMany() to link one model to many [OK]

Common Mistakes:

• Using belongsTo instead of hasMany
• Using hasOne for multiple related models
• Forgetting to return the relationship

3. Given the following models, what will $post->comments->count() output if the post has 3 related comments?

class Post extends Model {
  public function comments() {
    return $this->hasMany(Comment::class);
  }
}

medium

A. 0

B. An error

C. null

D. 3

Solution

1. Step 1: Understand hasMany returns a collection

   The comments() method returns all related Comment models as a collection.

2. Step 2: Count related comments

   Calling $post->comments->count() counts the number of related comments. Since there are 3, it returns 3.

3. Final Answer:

   3 -> Option D

4. Quick Check:

   Related comments count = 3 [OK]

Hint: hasMany returns collection; count() gives number of related items [OK]

Common Mistakes:

• Expecting count() to return null
• Confusing count() with count property
• Assuming hasMany returns a single model

4. What is wrong with this hasMany relationship definition?

public function comments() {
  return $this->hasMany('App\Models\Comment');
}

medium

A. The method should return an array, not a relationship

B. hasMany should be replaced with belongsTo

C. The model class should be imported or use ::class constant

D. The method must be static

Solution

1. Step 1: Check model reference style

   Using a string for model class works but is discouraged; better to import and use Comment::class.

2. Step 2: Identify best practice

   Importing the model and using Comment::class avoids typos and enables IDE support.

3. Final Answer:

   The model class should be imported or use ::class constant -> Option C

4. Quick Check:

   Use ::class for model references [OK]

Hint: Use ::class for model names, not strings [OK]

Common Mistakes:

• Using string class names without import
• Confusing hasMany with belongsTo
• Making relationship methods static

5. You have a User model and a Post model. Each user can have many posts. How do you retrieve all posts for a user with ID 5 using Eloquent's hasMany relationship?

hard

A. $posts = User::find(5)->posts;

B. $posts = Post::where('user_id', 5)->get();

C. $posts = User::posts()->where('id', 5)->get();

D. $posts = User::find(5)->hasMany(Post::class);

Solution

1. Step 1: Use find() to get user by ID

   User::find(5) fetches the user with ID 5.

2. Step 2: Access posts via hasMany relationship

   Accessing ->posts returns all posts related to that user.

3. Final Answer:

   $posts = User::find(5)->posts; -> Option A

4. Quick Check:

   Retrieve related posts via user->posts [OK]

Hint: Find user then access posts property [OK]

Common Mistakes:

• Calling hasMany() directly on model instance
• Using where on User model instead of Post
• Trying to call posts() statically