Why views present data in Ruby on Rails - Performance Evidence

Performance: Why views present data

MEDIUM IMPACT

This concept affects how quickly the page content appears and updates by controlling how data is rendered in the browser.

Rendering data in a Rails view efficiently

Ruby on Rails

<%= render partial: 'item', collection: @items %>

<!-- _item.html.erb -->
<div>
  <strong><%= item.name %></strong>
  <p><%= item.description %></p>
</div>

Using partials with collection rendering batches DOM updates and reduces repeated code, improving rendering efficiency.

📈 Performance GainSingle reflow for all items, reducing LCP and improving perceived load speed

Rendering data in a Rails view efficiently

Ruby on Rails

<% @items.each do |item| %>
  <div><%= item.name %></div>
  <div><%= item.description %></div>
<% end %>

Rendering many items with multiple elements causes the browser to process many DOM nodes and triggers multiple reflows.

📉 Performance CostTriggers N reflows where N is number of items, increasing LCP time

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Loop with inline ERB	Many nodes (2 per item)	N reflows (N = items)	High paint cost	[X] Bad
Partial with collection rendering	Fewer nodes, grouped	Single reflow	Lower paint cost	[OK] Good

Rendering Pipeline

Rails views generate HTML that the browser parses and renders. Efficient view code reduces the number of DOM nodes and layout recalculations.

→HTML Generation

→DOM Construction

→Layout

→Paint

⚠️ BottleneckLayout stage is most expensive when many DOM nodes are created or updated.

Core Web Vital Affected

LCP

This concept affects how quickly the page content appears and updates by controlling how data is rendered in the browser.

Optimization Tips

1Avoid rendering large loops inline in views to reduce DOM complexity.

2Use partials with collection rendering to batch DOM updates.

3Minimize the number of DOM nodes generated to speed up layout and paint.

Performance Quiz - 3 Questions

How does rendering many items directly in a Rails view affect page load?

A It increases layout recalculations and slows down LCP

B It reduces DOM nodes and speeds up rendering

C It has no effect on performance

D It improves browser caching

DevTools: Performance

How to check: Record a performance profile while loading the page, then inspect the 'Layout' and 'Recalculate Style' events to see how many times they occur.

What to look for: Look for fewer layout recalculations and shorter total layout time indicating efficient view rendering.

Practice

1. Why do views in Rails present data to users?

easy

A. To store data in the database

B. To turn raw data into readable web pages

C. To handle user login and authentication

D. To manage server configuration settings

Solution

1. Step 1: Understand the role of views in MVC

   Views are responsible for showing data to users in a readable format, usually as HTML pages.

2. Step 2: Differentiate views from other parts

   Controllers prepare data, models handle data storage, but views present data clearly to users.

3. Final Answer:

   To turn raw data into readable web pages -> Option B

4. Quick Check:

   Views present data = To turn raw data into readable web pages [OK]

Hint: Views display data as pages, not store or process it [OK]

Common Mistakes:

• Confusing views with controllers or models
• Thinking views handle data storage
• Assuming views manage server settings

2. Which of the following is the correct way to insert Ruby data into a Rails view using ERB syntax?

easy

A. <% @user.name %>

B. [[ @user.name ]]

C. {{ @user.name }}

D. <%= @user.name %>

Solution

1. Step 1: Identify ERB syntax for output

   In Rails views, <%= %> outputs Ruby code result into HTML.

2. Step 2: Compare options

   <% %> runs Ruby code but does not output it; {{ }} and [[ ]] are not Rails ERB syntax.

3. Final Answer:

   <%= @user.name %> -> Option D

4. Quick Check:

   ERB output tag = <%= @user.name %> [OK]

Hint: Use <%= %> to show Ruby data in views [OK]

Common Mistakes:

• Using <% %> which does not output data
• Confusing with other template syntaxes like {{ }}
• Forgetting to use equals sign for output

3. Given the controller sets @items = ['apple', 'banana', 'cherry'], what will this view code output?

<ul>
  <% @items.each do |item| %>
    <li><%= item.upcase %></li>
  <% end %>
</ul>

medium

A. APPLEBANANACHERRY

B. applebananacherry

C. ItemItemItem

D. Syntax error due to missing output tag

Solution

1. Step 1: Understand the loop and method

   The code loops over @items and outputs each item in uppercase inside <li> tags.

2. Step 2: Check output tags and method

   <%= item.upcase %> outputs the uppercase string; the loop is correct.

3. Final Answer:

   <ul><li>APPLE</li><li>BANANA</li><li>CHERRY</li></ul> -> Option A

4. Quick Check:

   Loop with upcase output =
   • APPLE
   • BANANA
   • CHERRY
   [OK]

Hint: Look for <%= %> to output transformed data inside loop [OK]

Common Mistakes:

• Confusing <% %> with <%= %> causing no output
• Ignoring the upcase method effect
• Assuming original lowercase output

4. Identify the error in this Rails view snippet:

<ul>
  <% @products.each do |product| %>
    <li><%= product.name %></li>
  <% end %>
</ul>

medium

A. No error, code is correct

B. Using <%= inside <% block without closing properly

C. Incorrect ERB output tag syntax

D. Missing closing tag for <li>

Solution

1. Step 1: Inspect ERB tags inside the loop

   The code uses proper ERB syntax: <% %> for the loop, <%= product.name %> for output, and HTML tags correctly placed.

2. Step 2: Verify no syntax issues

   All tags are properly opened and closed; no mixing of ERB and HTML incorrectly.

3. Final Answer:

   No error, code is correct -> Option A

4. Quick Check:

   Valid Rails ERB view code = No error, code is correct [OK]

Hint: Ensure ERB tags <%= %> wrap only Ruby code, not HTML [OK]

Common Mistakes:

• Placing HTML closing bracket inside ERB tag
• Confusing <% and <%= tags
• Assuming no syntax error when mixing tags

5. You want to display a list of users with their email only if the email is present. Which view code correctly presents this conditional data?

<ul>
  <% @users.each do |user| %>
    <li>
      <%= user.name %>
      <% if user.email.present? %>
        (<%= user.email %>)
      <% end %>
    </li>
  <% end %>
</ul>

hard

A. Syntax error due to missing output tags

B. Always shows email even if empty

C. Correctly shows name and email only if email exists

D. Does not loop through users properly

Solution

1. Step 1: Analyze the loop and conditional

   The code loops over @users and shows user.name always.

2. Step 2: Check conditional email display

   The if condition checks if email is present, then outputs it inside parentheses.

3. Step 3: Verify ERB syntax correctness

   Output tags <%= %> are used properly for name and email; control flow tags <% %> for condition.

4. Final Answer:

   Correctly shows name and email only if email exists -> Option C

5. Quick Check:

   Conditional display with correct ERB = Correctly shows name and email only if email exists [OK]

Hint: Use <% if %> for conditions, <%= %> to output data [OK]

Common Mistakes:

• Using <%= for if without closing properly
• Outputting email without checking presence
• Forgetting to close loop or condition tags