Aggregates (count, sum, avg) in Laravel - Performance & Optimization

Performance: Aggregates (count, sum, avg)

MEDIUM IMPACT

This affects how quickly the database returns summary data and how much data the server processes before sending results to the browser.

Calculating total number of users or sum of orders for display

Laravel

$count = User::count();
$sum = User::sum('orders_total');

Runs aggregate queries directly in the database, returning only the summary number quickly.

📈 Performance GainSingle fast query; minimal memory; faster LCP

Calculating total number of users or sum of orders for display

Laravel

$users = User::all();
$count = $users->count();
$sum = $users->sum('orders_total');

Loads all user records into memory before counting or summing, causing slow queries and high memory use.

📉 Performance CostBlocks rendering while loading all rows; high memory usage; slower LCP

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Loading full dataset then counting/summing in PHP	N/A (server-side)	N/A	N/A	[X] Bad
Using database aggregate functions (count, sum, avg)	N/A (server-side)	N/A	N/A	[OK] Good

Rendering Pipeline

Aggregate queries reduce data sent from server to browser, speeding up data processing and rendering.

→Data Fetching

→Server Processing

→Network Transfer

→Rendering

⚠️ BottleneckData Fetching and Server Processing when loading full datasets unnecessarily

Core Web Vital Affected

LCP

This affects how quickly the database returns summary data and how much data the server processes before sending results to the browser.

Optimization Tips

1Always use database aggregate functions instead of loading full datasets for counts or sums.

2Avoid fetching unnecessary rows to reduce server memory and processing time.

3Smaller query results speed up network transfer and improve page load times.

Performance Quiz - 3 Questions

Why is using User::count() better than loading all users and then counting in Laravel?

A It caches all user data in memory.

B It runs a single optimized query returning only the count number.

C It loads all user data faster.

D It delays the query until rendering.

DevTools: Network

How to check: Open DevTools, go to Network tab, filter XHR requests, and inspect the response size and time for aggregate queries.

What to look for: Smaller response size and faster response time indicate efficient aggregate queries.

Practice

1. What does the count() method do in Laravel Eloquent?

easy

A. Returns the number of records matching the query

B. Calculates the sum of a column

C. Finds the average value of a column

D. Deletes all records in the table

Solution

1. Step 1: Understand the purpose of count()

   The count() method counts how many records match the query conditions.

2. Step 2: Compare with other aggregate methods

   Unlike sum() or avg(), count() returns a number of rows, not a calculation on column values.

3. Final Answer:

   Returns the number of records matching the query -> Option A

4. Quick Check:

   count() = number of records [OK]

Hint: count() counts rows, sum() and avg() work on columns [OK]

Common Mistakes:

• Confusing count() with sum() or avg()
• Thinking count() returns column values
• Assuming count() deletes records

2. Which of the following is the correct syntax to get the sum of the price column using Eloquent?

easy

A. Product::sum(['price']);

B. Product::sum(price);

C. Product->sum('price');

D. Product::sum('price');

Solution

1. Step 1: Identify correct method call syntax

   In Laravel Eloquent, static calls use double colon :: and column names must be strings in quotes.

2. Step 2: Check each option

   Product::sum('price'); uses Product::sum('price'); which is correct. Product::sum(price); misses quotes, C uses arrow on class, D passes array incorrectly.

3. Final Answer:

   Product::sum('price'); -> Option D

4. Quick Check:

   sum('column') needs quotes and :: [OK]

Hint: Use quotes around column name and :: for static call [OK]

Common Mistakes:

• Omitting quotes around column name
• Using -> instead of :: on model class
• Passing column name as array

3. Given the code:

$total = Order::where('status', 'completed')->sum('amount');

What does $total contain?

medium

A. The count of orders with status 'completed'

B. An error because sum() cannot be used with where()

C. The sum of 'amount' for orders with status 'completed'

D. The average 'amount' for all orders

Solution

1. Step 1: Understand the query filter

   The where('status', 'completed') filters orders to only those completed.

2. Step 2: Apply the sum aggregate

   The sum('amount') adds up the 'amount' values of the filtered orders.

3. Final Answer:

   The sum of 'amount' for orders with status 'completed' -> Option C

4. Quick Check:

   where() filters, sum() adds column values [OK]

Hint: where() filters rows, sum() adds column values of filtered rows [OK]

Common Mistakes:

• Thinking sum() returns count of rows
• Believing sum() cannot be chained with where()
• Confusing sum() with avg()

4. What is wrong with this code snippet?

$average = User::avg(age);

medium

A. avg() requires a second parameter

B. Missing quotes around the column name 'age'

C. avg() cannot be used on User model

D. Using avg() without where() causes error

Solution

1. Step 1: Check method parameter syntax

   The avg() method requires the column name as a string, so it must be quoted.

2. Step 2: Identify the error cause

   Without quotes, PHP treats age as a constant or variable, causing an error or unexpected behavior.

3. Final Answer:

   Missing quotes around the column name 'age' -> Option B

4. Quick Check:

   Column names must be strings in quotes [OK]

Hint: Always quote column names in aggregate methods [OK]

Common Mistakes:

• Omitting quotes around column names
• Thinking avg() needs multiple parameters
• Assuming avg() requires where()

5. You want to get the average price of products that are in stock (stock > 0). Which Eloquent query is correct?

hard

A. Product::where('stock', '>', 0)->avg('price');

B. Product::avg('price')->where('stock', '>', 0);

C. Product::where('stock', '>', 0)->sum('price') / Product::count();

D. Product::sum('price')->where('stock', '>', 0) / Product::count();

Solution

1. Step 1: Filter products with stock > 0

   The where('stock', '>', 0) filters only products that are in stock.

2. Step 2: Calculate average price of filtered products

   The avg('price') calculates the average price of those filtered products.

3. Step 3: Check other options for correctness

   Product::avg('price')->where('stock', '>', 0); calls avg() before where(), which is invalid. Manual calculations with sum divided by count do not filter correctly or mix sum and count improperly.

4. Final Answer:

   Product::where('stock', '>', 0)->avg('price'); -> Option A

5. Quick Check:

   Filter first, then aggregate [OK]

Hint: Chain where() before avg() to filter then calculate [OK]

Common Mistakes:

• Calling aggregate before where()
• Manually dividing sum by count without filtering
• Mixing sum() and avg() incorrectly