Partial templates in Ruby on Rails - Performance & Optimization

Performance: Partial templates

MEDIUM IMPACT

Partial templates affect page load speed by controlling how much HTML is rendered and reused, impacting server response time and browser rendering.

Rendering repeated UI elements in a Rails view

Ruby on Rails

<%= render 'items', items: @items %> <!-- Render a single partial that loops internally -->

Rendering one partial that loops internally reduces rendering calls, lowering server load.

📈 Performance GainSingle template render regardless of item count, reducing server CPU and response time

Rendering repeated UI elements in a Rails view

Ruby on Rails

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

Rendering a partial for each item individually triggers multiple rendering calls, increasing server CPU and response time.

📉 Performance CostTriggers N template renders and increases server response time linearly with N items

Performance Comparison

Pattern	DOM Operations	Render Calls	Paint Cost	Verdict
Many small partial renders	N partial renders	N render calls	Higher paint delay due to slower HTML delivery	[X] Bad
Single partial with internal loop	1 partial render	1 render call	Faster paint due to quicker HTML delivery	[OK] Good

Rendering Pipeline

Partial templates are processed on the server during view rendering, generating HTML sent to the browser. More partials mean more server CPU and slower HTML generation, which delays browser painting.

→Server Rendering

→Network Transfer

→Browser Paint

⚠️ BottleneckServer Rendering (template processing)

Core Web Vital Affected

LCP

Partial templates affect page load speed by controlling how much HTML is rendered and reused, impacting server response time and browser rendering.

Optimization Tips

1Avoid rendering many small partials separately; combine logic when possible.

2Use a single partial with internal loops to reduce server rendering overhead.

3Cache partial outputs if content does not change often to speed up response.

Performance Quiz - 3 Questions

What is the main performance cost of rendering many small partial templates in Rails?

A Larger JavaScript bundle size

B More CSS reflows in the browser

C Increased server CPU and slower HTML generation

D Slower image loading

DevTools: Network

How to check: Open DevTools, go to Network tab, reload page, and check the time to first byte and content download size for HTML response.

What to look for: Long server response time or large HTML size indicates inefficient partial rendering.

Practice

1. What is the main purpose of using partial templates in Rails views?

easy

A. To define routes for the application

B. To speed up database queries

C. To handle user authentication

D. To reuse small pieces of view code across different pages

Solution

1. Step 1: Understand what partial templates are

   Partial templates are small view files that can be included in other views to avoid repeating code.

2. Step 2: Identify the main use case

   The main use is to reuse small pieces of view code across different pages, improving maintainability.

3. Final Answer:

   To reuse small pieces of view code across different pages -> Option D

4. Quick Check:

   Partial templates = reuse view code [OK]

Hint: Partial templates reuse view parts, not logic or routes [OK]

Common Mistakes:

• Thinking partials speed up database queries
• Confusing partials with authentication logic
• Assuming partials define routes

2. Which of the following is the correct syntax to render a partial named _menu.html.erb in a Rails view?

easy

A. <%= partial 'menu' %>

B. <%= render 'menu' %>

C. <%= include 'menu' %>

D. <%= render_partial 'menu' %>

Solution

1. Step 1: Recall the Rails partial rendering syntax

   Rails uses render 'partial_name' to include partials, omitting the underscore and file extension.

2. Step 2: Match the correct syntax

   The correct syntax is <%= render 'menu' %> to render _menu.html.erb.

3. Final Answer:

   <%= render 'menu' %> -> Option B

4. Quick Check:

   Render partial = render 'name' [OK]

Hint: Use render 'partial_name' without underscore or extension [OK]

Common Mistakes:

• Using 'partial' instead of 'render'
• Using 'include' which is not a Rails helper
• Adding underscore in render argument

3. Given the following code in a Rails view:

<%= render partial: 'product', collection: @products, as: :item %>

What will be the local variable name inside the _product.html.erb partial for each item?

medium

A. item

B. product

C. @products

D. collection

Solution

1. Step 1: Understand collection rendering with 'as'

   When rendering a collection with render partial: 'name', collection: ..., as: :var, each element is passed as var inside the partial.

2. Step 2: Identify the local variable name

   Here, as: :item means inside _product.html.erb each element is accessible as item.

3. Final Answer:

   item -> Option A

4. Quick Check:

   Collection with 'as' sets local variable name [OK]

Hint: Use 'as' option to rename local variable in collection partial [OK]

Common Mistakes:

• Assuming default variable name 'product' instead of 'item'
• Using instance variable '@products' inside partial
• Confusing 'collection' as variable name

4. What is wrong with this code snippet in a Rails view?

<%= render 'user', user: @user %>

Assuming the partial is named _user.html.erb and expects a local variable user.

medium

A. The syntax should be render partial: 'user', locals: { user: @user }

B. The partial name should include the underscore: render '_user'

C. The code is correct and will work as expected

D. You cannot pass local variables to partials

Solution

1. Step 1: Check the shorthand syntax for passing locals

   Rails allows passing locals directly by naming the variable in the render call, like render 'user', user: @user.

2. Step 2: Confirm partial naming rules

   The underscore is omitted in the render call; Rails finds _user.html.erb automatically.

3. Final Answer:

   The code is correct and will work as expected -> Option C

4. Quick Check:

   Passing locals shorthand is valid [OK]

Hint: Passing locals as named args in render is valid shorthand [OK]

Common Mistakes:

• Thinking underscore is required in render argument
• Believing locals must be inside a hash named 'locals'
• Assuming locals cannot be passed at all

5. You want to render a list of comments using a partial _comment.html.erb. Each comment should be passed as comment local variable. Which is the best way to do this in Rails?

hard

A. <%= render partial: 'comment', collection: @comments %>

B. <%= render 'comment', comments: @comments %>

C. <%= render partial: 'comment', collection: @comments, as: :comments %>

D. <%= render partial: 'comment', locals: { comment: @comments } %>

Solution

1. Step 1: Understand collection rendering default variable

   When rendering a collection with render partial: 'comment', collection: @comments, Rails passes each element as comment by default (partial name without underscore).

2. Step 2: Evaluate other options

   <%= render 'comment', comments: @comments %> passes the whole array as a single local, not each comment. <%= render partial: 'comment', collection: @comments, as: :comments %> passes each as comments (plural). <%= render partial: 'comment', locals: { comment: @comments } %> passes the entire array as one variable, not individual comments.

3. Final Answer:

   <%= render partial: 'comment', collection: @comments %> -> Option A

4. Quick Check:

   Collection rendering uses partial name as local by default [OK]

Hint: Render collection with partial name to get default local variable [OK]

Common Mistakes:

• Passing whole array as one local variable
• Using 'as: :comments' which sets plural local name
• Confusing locals hash with collection rendering