Why models represent data in Ruby on Rails - Performance Evidence

Performance: Why models represent data

MEDIUM IMPACT

This concept affects how efficiently data is managed and accessed in a Rails application, impacting server response time and page load speed.

Managing user data in a Rails app

Ruby on Rails

def user_name
  @user ||= User.find(params[:id])
  @user.name
end

Caches the user object on first call, avoiding repeated database queries.

📈 Performance Gainsingle database query per request, faster response, better LCP

Managing user data in a Rails app

Ruby on Rails

def user_name
  User.find(params[:id]).name
end

This code queries the database every time the method is called, causing repeated database hits.

📉 Performance Costtriggers multiple database queries, increasing server response time and slowing LCP

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Repeated database calls without caching	N/A	N/A	Blocks rendering due to slow server response	[X] Bad
Model caching with memoization	N/A	N/A	Faster server response enables quicker paint	[OK] Good

Rendering Pipeline

Models handle data retrieval and business logic before the view renders content. Efficient model use reduces database calls and speeds up server response, which helps the browser start rendering sooner.

→Server Processing

→Data Fetching

→HTML Rendering

⚠️ BottleneckDatabase queries triggered by model calls

Core Web Vital Affected

LCP

This concept affects how efficiently data is managed and accessed in a Rails application, impacting server response time and page load speed.

Optimization Tips

1Avoid repeated database queries by caching model data during a request.

2Use models to organize data access and reduce server processing time.

3Eager load related data in models to minimize query count and speed up page rendering.

Performance Quiz - 3 Questions

How does using models to represent data affect page load speed in Rails?

A It has no effect on page load speed.

B It reduces repeated database queries, speeding up server response.

C It increases the number of database queries, slowing down the server.

D It only affects client-side rendering, not server response.

DevTools: Network

How to check: Open DevTools, go to Network tab, reload the page, and observe the number and timing of API/database requests.

What to look for: Look for repeated or slow database queries that delay the initial HTML response, which slows LCP.