Query interface basics in Ruby on Rails - Performance & Optimization

Performance: Query interface basics

MEDIUM IMPACT

This affects how quickly the database queries run and how fast the page loads data from the database.

Fetching user records with conditions

Ruby on Rails

User.where(active: true)

Filters users at the database level, returning only needed records quickly.

📈 Performance GainReduces data transferred; faster query execution; improves LCP

Fetching user records with conditions

Ruby on Rails

User.all.select { |u| u.active? }

Loads all users into memory then filters, causing slow response and high memory use.

📉 Performance CostBlocks rendering until all users load; high memory use; slow database response

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Loading all records then filtering in Ruby	N/A	N/A	Blocks rendering due to slow data fetch	[X] Bad
Filtering records in database query	N/A	N/A	Faster data fetch enables quicker rendering	[OK] Good

Rendering Pipeline

The query interface sends SQL commands to the database, which returns data for rendering. Efficient queries reduce database processing and data transfer, speeding up rendering.

→Data Fetching

→Rendering

⚠️ BottleneckDatabase query execution and data transfer

Core Web Vital Affected

LCP

This affects how quickly the database queries run and how fast the page loads data from the database.

Optimization Tips

1Always filter data in the database query, not in Ruby after loading.

2Limit the number of records and columns fetched to reduce payload size.

3Use database indexes to speed up query execution.

Performance Quiz - 3 Questions

Why is filtering records in the database query better than filtering in Ruby after loading all records?

A Because Ruby filtering uses less memory

B Because database queries always run faster than Ruby code

C Because it reduces data transferred and speeds up query execution

D Because filtering in Ruby triggers fewer reflows

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page, and inspect the database query API call timing and payload size.

What to look for: Look for large payloads or slow response times indicating inefficient queries.