Nested attributes in Ruby on Rails - Performance & Optimization

Performance: Nested attributes

MEDIUM IMPACT

Nested attributes affect server response time and client rendering when handling complex forms with multiple associated records.

Handling multiple associated records in a form

Ruby on Rails

class Project < ApplicationRecord
  has_many :tasks
  accepts_nested_attributes_for :tasks
end

# In the form view:
<%= form_with model: @project do |f| %>
  <%= f.fields_for :tasks do |task_fields| %>
    <%= task_fields.text_field :name %>
  <% end %>
  <%= link_to 'Add Task', '#', id: 'add-task' %>
<% end %>

# Use JavaScript to add tasks dynamically instead of loading all at once

Limits initial DOM size and HTML payload, reducing initial load time and reflows; defers adding more tasks to user interaction.

📈 Performance GainReduces initial reflows and paint; improves LCP by loading fewer elements upfront.

Handling multiple associated records in a form

Ruby on Rails

class Project < ApplicationRecord
  has_many :tasks
  accepts_nested_attributes_for :tasks
end

# In the form view:
<%= form_with model: @project do |f| %>
  <%= f.fields_for :tasks do |task_fields| %>
    <%= task_fields.text_field :name %>
  <% end %>
<% end %>

# Loads all tasks without pagination or limits

Loading and rendering all associated tasks at once can create a very large DOM and slow down page load and rendering.

📉 Performance CostTriggers many DOM nodes and reflows proportional to number of tasks; large HTML payload increases LCP.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Render all nested records at once	High number of nodes	Multiple reflows proportional to records	High paint cost due to large DOM	[X] Bad
Limit nested records and add dynamically	Reduced nodes initially	Single reflow on load	Lower paint cost	[OK] Good

Rendering Pipeline

Nested attributes generate HTML for associated records which the browser must parse, style, layout, and paint. Large nested forms increase DOM size and complexity, impacting layout and paint stages.

→DOM Construction

→Style Calculation

→Layout

→Paint

⚠️ BottleneckLayout stage is most expensive due to large and complex nested DOM trees.

Core Web Vital Affected

LCP

Nested attributes affect server response time and client rendering when handling complex forms with multiple associated records.

Optimization Tips

1Limit the number of nested records rendered initially to reduce DOM size.

2Use JavaScript to add nested fields dynamically after initial load.

3Avoid rendering all nested attributes at once to improve LCP.

Performance Quiz - 3 Questions

What is a main performance risk when rendering many nested attributes in a Rails form?

A Too many database queries on form submit

B JavaScript errors from nested fields

C Large DOM causing slow layout and paint

D Missing ARIA labels on inputs

DevTools: Performance

How to check: Record a page load with nested attributes form open; analyze Main thread activity and Layout events.

What to look for: Look for long Layout and Paint tasks indicating heavy DOM and style recalculations from large nested forms.

Practice

1. What does accepts_nested_attributes_for do in a Rails model?

easy

A. Validates the presence of nested attributes in the parent model.

B. Creates a new database table for nested models automatically.

C. Allows a parent model to accept and save attributes for its associated child models.

D. Generates controller actions for nested resources.

Solution

1. Step 1: Understand the purpose of accepts_nested_attributes_for

   This method is used in a parent model to allow it to accept attributes for its associated child models.

2. Step 2: Recognize what it enables in Rails

   It enables saving or updating child model data through the parent model's form or controller.

3. Final Answer:

   Allows a parent model to accept and save attributes for its associated child models. -> Option C

4. Quick Check:

   accepts_nested_attributes_for = Accept nested child attributes [OK]

Hint: Think: parent model saving child data together [OK]

Common Mistakes:

• Confusing it with database table creation
• Assuming it validates nested attributes automatically
• Thinking it generates controller code

2. Which of the following is the correct syntax to enable nested attributes for a child model named tasks inside a parent model?

easy

A. accepts_nested_attributes_for :tasks

B. accepts_nested_attributes_for :task

C. accepts_nested_attributes_for tasks

D. accepts_nested_attributes_for 'tasks'

Solution

1. Step 1: Identify the correct argument type

   The method expects a symbol representing the association name, which is plural if the association is has_many.

2. Step 2: Match the association name

   Since the child model is tasks (plural), the correct syntax is accepts_nested_attributes_for :tasks.

3. Final Answer:

   accepts_nested_attributes_for :tasks -> Option A

4. Quick Check:

   Use symbol with plural association name [OK]

Hint: Use symbol and plural for has_many associations [OK]

Common Mistakes:

• Using singular instead of plural for has_many
• Passing string instead of symbol
• Omitting colon before association name

3. Given the following models and controller snippet, what will happen when creating a Project with nested tasks_attributes?

class Project < ApplicationRecord
  has_many :tasks
  accepts_nested_attributes_for :tasks
end

class Task < ApplicationRecord
  belongs_to :project
end

# In ProjectsController
params = { project: { name: 'Build App', tasks_attributes: [{ title: 'Design UI' }, { title: 'Write Tests' }] } }
@project = Project.new(params[:project])
@project.save

medium

A. A new project and two associated tasks will be saved in the database.

B. Only the project will be saved; tasks will be ignored.

C. An error will occur because nested attributes are not permitted in the controller.

D. The project will save but tasks will be saved without association.

Solution

1. Step 1: Check model setup for nested attributes

   The Project model uses accepts_nested_attributes_for :tasks, allowing nested task attributes.

2. Step 2: Analyze controller params and save

   The params include tasks_attributes with two tasks. Calling Project.new with these params and then save will save the project and its tasks together.

3. Final Answer:

   A new project and two associated tasks will be saved in the database. -> Option A

4. Quick Check:

   Nested attributes save parent and children together [OK]

Hint: Nested attributes save parent and children in one go [OK]

Common Mistakes:

• Assuming tasks are ignored without explicit permit
• Thinking save fails without controller strong params shown
• Believing tasks save without association

4. Identify the error in the following controller code when trying to save nested attributes:

def project_params
  params.require(:project).permit(:name, tasks_attributes: [:title])
end

@project = Project.new(project_params)
@project.save

Assuming the models are set up correctly with accepts_nested_attributes_for :tasks.

medium

A. The require method should be permit instead.

B. The accepts_nested_attributes_for should be in the controller, not the model.

C. The tasks_attributes key should be a string, not a symbol.

D. The permit method is missing the :id key inside tasks_attributes.

Solution

1. Step 1: Understand strong parameters for nested attributes

   When updating nested records, Rails expects the :id key to identify existing child records.

2. Step 2: Check the permit call

   The permit call only allows :title inside tasks_attributes, missing :id. This causes update failures or errors.

3. Final Answer:

   The permit method is missing the :id key inside tasks_attributes. -> Option D

4. Quick Check:

   Permit :id for nested updates [OK]

Hint: Permit :id inside nested attributes for updates [OK]

Common Mistakes:

• Omitting :id in nested strong params
• Confusing require and permit methods
• Placing accepts_nested_attributes_for in controller

5. You have a Survey model with many questions. You want to allow users to add, update, and remove questions through the survey form. Which combination of code is needed to correctly handle nested attributes and allow question removal?

hard

A. In Survey model: accepts_nested_attributes_for :questions, reject_if: :all_blank
In controller: permit questions_attributes with :content, :_destroy

B. In Survey model: accepts_nested_attributes_for :questions, allow_destroy: true
In controller: permit questions_attributes with :id, :content, :_destroy

C. In Survey model: has_many :questions
In controller: permit questions_attributes with :id, :content

D. In Survey model: accepts_nested_attributes_for :questions
In controller: permit questions_attributes with :content only

Solution

1. Step 1: Enable nested attributes with destroy option

   To allow removal of nested records, accepts_nested_attributes_for must include allow_destroy: true.

2. Step 2: Permit necessary keys in controller

   The controller must permit :id to identify records, :content for data, and :_destroy to mark records for deletion.

3. Final Answer:

   In Survey model: accepts_nested_attributes_for :questions, allow_destroy: true In controller: permit questions_attributes with :id, :content, :_destroy -> Option B

4. Quick Check:

   allow_destroy and permit :_destroy for removals [OK]

Hint: Use allow_destroy and permit :_destroy to remove nested records [OK]

Common Mistakes:

• Forgetting allow_destroy in model
• Not permitting :_destroy in strong params
• Permitting only :content without :id