Database query optimization in Ruby on Rails - Performance & Optimization

Performance: Database query optimization

HIGH IMPACT

This affects how fast the page loads data from the database and how quickly the server responds to user requests.

Fetching related records in a Rails app

Ruby on Rails

posts = Post.includes(:comments).all
posts.each do |post|
  puts post.comments.size
end

Loads all comments in one query, avoiding multiple database hits.

📈 Performance Gainreduces queries from N+1 to 2, significantly lowering server response time

Fetching related records in a Rails app

Ruby on Rails

posts = Post.all
posts.each do |post|
  puts post.comments.count
end

This triggers a separate database query for each post to count comments, causing many queries.

📉 Performance Costtriggers N+1 queries where N is number of posts, increasing server response time

Performance Comparison

Pattern	Database Queries	Data Transferred	Server Response Time	Verdict
N+1 queries	Many small queries (N+1)	More data due to repeated queries	High due to multiple DB hits	[X] Bad
Eager loading with includes	Few queries (usually 2)	Less repeated data	Lower due to fewer DB hits	[OK] Good
Selecting all columns	Single query	Large data size	Medium due to data size	[!] OK
Selecting needed columns	Single query	Minimal data size	Low due to less data	[OK] Good
Unindexed where clause	Single query	Depends on data	High due to full table scan	[X] Bad
Indexed where clause	Single query	Depends on data	Low due to index use	[OK] Good

Rendering Pipeline

Database query optimization reduces server processing time before HTML is sent to the browser, improving the critical rendering path by delivering data faster.

→Server Processing

→Network Transfer

→First Contentful Paint

⚠️ BottleneckServer Processing due to slow or excessive database queries

Core Web Vital Affected

LCP

This affects how fast the page loads data from the database and how quickly the server responds to user requests.

Optimization Tips

1Avoid N+1 queries by using eager loading (includes).

2Select only the columns you need to reduce data size.

3Add indexes on columns used frequently in filters.

Performance Quiz - 3 Questions

What is the main performance problem with N+1 queries in Rails?

A It triggers many database queries, slowing server response

B It loads too many columns in one query

C It causes layout shifts in the browser

D It increases CSS selector complexity

DevTools: Network and Performance panels

How to check: Open DevTools, go to Network tab, reload page and check time for API/database calls; use Performance tab to record and analyze server response times.

What to look for: Look for long waiting times on database calls and multiple repeated requests indicating N+1 queries.