Select and pluck in Ruby on Rails - Performance & Optimization

Performance: Select and pluck

MEDIUM IMPACT

This affects how efficiently data is fetched from the database and how much data is sent to the app, impacting page load speed and server response time.

Fetching specific columns from a database table

Ruby on Rails

User.pluck(:name)

Pluck fetches only the requested column directly from the database as an array, reducing memory and processing.

📈 Performance GainReduces data transfer size and CPU usage, improving response time and LCP.

Fetching specific columns from a database table

Ruby on Rails

User.select(:id, :name).map(&:name)

Select loads full ActiveRecord objects with selected attributes, then map extracts data, causing extra memory and processing.

📉 Performance CostAdds unnecessary object instantiation and memory use, increasing server response time.

Performance Comparison

Pattern	Data Fetched	Server Processing	Network Payload	Verdict
select + map	AR objects with selected columns	High (object creation)	Large	[X] Bad
pluck	Only requested columns	Low (direct array)	Small	[OK] Good

Rendering Pipeline

Data fetching with select loads full objects causing more server processing and larger payloads, delaying response. Pluck fetches minimal data, speeding up server response and page load.

→Server Processing

→Network Transfer

→Rendering

⚠️ BottleneckServer Processing and Network Transfer

Core Web Vital Affected

LCP

This affects how efficiently data is fetched from the database and how much data is sent to the app, impacting page load speed and server response time.

Optimization Tips

1Use pluck to fetch only needed columns to reduce data size.

2Avoid select with map for simple column extraction to save memory and CPU.

3Smaller data payloads improve server response and page load speed.

Performance Quiz - 3 Questions

Which method fetches only specific columns directly from the database, reducing data load?

A select + map

B pluck

C all

D find

DevTools: Network

How to check: Open DevTools, go to Network tab, filter for XHR or fetch requests, inspect the response payload size and content for database queries.

What to look for: Smaller payload size and faster response times indicate efficient data fetching with pluck.