Ordering and grouping in Laravel - Performance & Optimization

Performance: Ordering and grouping

MEDIUM IMPACT

Ordering and grouping affect how quickly the database returns sorted or aggregated data, impacting page load speed and responsiveness.

Fetching sorted and grouped data for display

Laravel

DB::table('orders')->groupBy('status')->orderBy('created_at')->get();

Sorting and grouping are done in the database, which is optimized for these operations, reducing data transferred and processing time.

📈 Performance GainFaster query execution; reduces data transferred; improves LCP

Fetching sorted and grouped data for display

Laravel

DB::table('orders')->get()->sortBy('created_at')->groupBy('status');

Sorting and grouping are done in PHP after fetching all records, causing high memory use and slow response.

📉 Performance CostBlocks rendering until all data is fetched and processed; high memory usage

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Ordering and grouping in PHP after fetch	N/A	N/A	Blocks rendering until data ready	[X] Bad
Ordering and grouping in database query	N/A	N/A	Faster data ready for rendering	[OK] Good

Rendering Pipeline

Ordering and grouping affect the data retrieval stage before rendering. Efficient queries reduce time waiting for data, speeding up the critical rendering path.

→Data Fetching

→Rendering

→Layout

⚠️ BottleneckData Fetching (database query execution time)

Core Web Vital Affected

LCP

Ordering and grouping affect how quickly the database returns sorted or aggregated data, impacting page load speed and responsiveness.

Optimization Tips

1Always perform ordering and grouping in the database query, not in PHP after fetching.

2Avoid fetching large datasets before sorting or grouping to reduce memory and CPU load.

3Use database indexes on columns used for ordering and grouping to speed up queries.

Performance Quiz - 3 Questions

Where should ordering and grouping be done for best performance in Laravel?

A After fetching data in PHP using collection methods

B In JavaScript after page load

C In the database query using orderBy and groupBy

D In the view template

DevTools: Network and Performance

How to check: Open DevTools, go to Network tab, filter XHR requests, check query response times; then use Performance tab to see when content renders.

What to look for: Look for long database query response times delaying content load; faster queries improve Largest Contentful Paint.

Practice

1. What does the orderBy method do in Laravel's Eloquent?

easy

A. Sorts the query results by a specified column

B. Groups the query results by a specified column

C. Filters the query results by a condition

D. Joins two tables in the query

Solution

1. Step 1: Understand the purpose of orderBy

   The orderBy method is used to sort query results by a column in ascending or descending order.

2. Step 2: Differentiate from grouping and filtering

   Grouping collects rows with the same value, filtering limits rows by condition, and joining combines tables. These are different from sorting.

3. Final Answer:

   Sorts the query results by a specified column -> Option A

4. Quick Check:

   Ordering = Sorting [OK]

Hint: Remember: orderBy sorts, groupBy groups data [OK]

Common Mistakes:

• Confusing orderBy with groupBy
• Thinking orderBy filters data
• Mixing orderBy with join operations

2. Which of the following is the correct syntax to order users by their created_at date descending in Laravel?

easy

A. User::order('created_at', 'desc')->get();

B. User::orderBy('created_at', 'desc')->get();

C. User::groupBy('created_at')->desc()->get();

D. User::sortBy('created_at', 'desc')->get();

Solution

1. Step 1: Identify correct method for ordering

   Laravel uses orderBy with column and direction as parameters to sort results.

2. Step 2: Check method chaining and spelling

   orderBy is correct, desc is lowercase string, and get() fetches results. Other options use invalid methods.

3. Final Answer:

   User::orderBy('created_at', 'desc')->get(); -> Option B

4. Quick Check:

   Correct syntax = User::orderBy('created_at', 'desc')->get(); [OK]

Hint: Use orderBy('column', 'desc') to sort descending [OK]

Common Mistakes:

• Using groupBy instead of orderBy
• Using order() or sortBy() which don't exist in Eloquent
• Incorrect method chaining order

3. Given the code:

$results = DB::table('orders')
  ->select('status', DB::raw('count(*) as total'))
  ->groupBy('status')
  ->orderBy('total', 'desc')
  ->get();

What will $results contain?

medium

A. A list of orders sorted by status alphabetically

B. An error because you cannot order by an alias

C. A list of orders grouped by status without counts

D. A list of statuses with their order counts sorted descending by count

Solution

1. Step 1: Understand grouping and counting

   The query groups orders by status and counts how many orders each status has, naming count as total.

2. Step 2: Analyze ordering by count

   The results are ordered by total descending, so statuses with more orders appear first.

3. Final Answer:

   A list of statuses with their order counts sorted descending by count -> Option D

4. Quick Check:

   Group + count + orderBy total desc = A list of statuses with their order counts sorted descending by count [OK]

Hint: groupBy + count + orderBy alias works in Laravel [OK]

Common Mistakes:

• Thinking orderBy sorts by status alphabetically
• Missing that count(*) is aliased as total
• Assuming ordering by alias causes error

4. What is wrong with this Laravel query?

$users = User::groupBy('role')->orderBy('name')->get();

medium

A. Ordering by 'name' is invalid because 'name' is not in groupBy

B. Nothing is wrong; this query works fine

C. groupBy requires an aggregate function with orderBy

D. You cannot use orderBy after groupBy

Solution

1. Step 1: Understand SQL grouping rules

   When grouping by a column, all selected columns must be in groupBy or aggregated. Ordering by a column not in groupBy can cause errors.

2. Step 2: Check if 'name' is grouped or aggregated

   The query groups by 'role' but orders by 'name' which is not grouped or aggregated, causing SQL errors.

3. Final Answer:

   Ordering by 'name' is invalid because 'name' is not in groupBy -> Option A

4. Quick Check:

   Order column must be grouped or aggregated [OK]

Hint: Order columns must be in groupBy or aggregated [OK]

Common Mistakes:

• Assuming orderBy always works after groupBy
• Ignoring SQL strict mode errors
• Thinking groupBy requires aggregate with orderBy

5. You want to get the total sales amount per product category, but only for categories with more than 5 sales, ordered by total sales descending. Which Laravel query achieves this?

hard

A. DB::table('sales')->select('category', DB::raw('sum(amount) as total'))
->orderBy('total', 'desc')->groupBy('category')->having('total', '>', 5)
->get();

B. DB::table('sales')->select('category', DB::raw('sum(amount) as total'))
->groupBy('category')->where('total', '>', 5)
->orderBy('total', 'desc')->get();

C. DB::table('sales')->select('category', DB::raw('sum(amount) as total'))
->groupBy('category')->having('total', '>', 5)
->orderBy('total', 'desc')->get();

D. DB::table('sales')->select('category', DB::raw('sum(amount) as total'))
->groupBy('category')->orderBy('total', 'desc')->where('total', '>', 5)
->get();

Solution

1. Step 1: Use groupBy and sum aggregation

   Group sales by category and sum the amount as total.

2. Step 2: Filter groups with having clause

   Use having('total', '>', 5) to filter categories with more than 5 sales. where cannot filter aggregated results.

3. Step 3: Order results by total descending

   Use orderBy('total', 'desc') after grouping and filtering.

4. Final Answer:

   DB::table('sales')->select('category', DB::raw('sum(amount) as total')) ->groupBy('category')->having('total', '>', 5) ->orderBy('total', 'desc')->get(); -> Option C

5. Quick Check:

   Use having for aggregates, orderBy after groupBy [OK]

Hint: Use having() to filter grouped aggregates, not where() [OK]

Common Mistakes:

• Using where() instead of having() for aggregate filters
• Ordering before grouping
• Misplacing having() after where()