Callbacks overview in Ruby on Rails - Performance & Optimization

Performance: Callbacks overview

MEDIUM IMPACT

Callbacks affect the server response time and database transaction speed by adding extra processing steps during model lifecycle events.

Running complex logic on every model save

Ruby on Rails

class User < ApplicationRecord
  after_commit :enqueue_heavy_job

  def enqueue_heavy_job
    HeavyJob.perform_later(self.id)
  end
end

Moves heavy work to background job, keeping request fast and non-blocking.

📈 Performance Gainreduces request blocking to near zero, improves server throughput

Running complex logic on every model save

Ruby on Rails

class User < ApplicationRecord
  before_save :heavy_computation

  def heavy_computation
    # complex calculations or external API calls
  end
end

This callback runs heavy logic on every save, blocking the request and increasing response time.

📉 Performance Costblocks server response for 100+ ms per save, increasing request latency

Performance Comparison

Pattern	Server Processing	Database Impact	Response Delay	Verdict
Heavy logic in before_save	High CPU usage	Blocks transaction	Increases latency	[X] Bad
Lightweight after_commit with background job	Minimal CPU	Non-blocking	Fast response	[OK] Good

Rendering Pipeline

Rails callbacks run during model lifecycle events before or after database operations, affecting server processing time before response is sent.

→Model Validation

→Database Transaction

→Controller Response

⚠️ BottleneckHeavy or synchronous callbacks block database transactions and delay response.

Optimization Tips

1Avoid heavy or blocking logic in before_save or before_create callbacks.

2Use after_commit callbacks to trigger background jobs for heavy tasks.

3Monitor callback execution time to prevent slow server responses.

Performance Quiz - 3 Questions

What is the main performance risk of using heavy logic in before_save callbacks?

A It increases CSS paint time.

B It causes visual layout shifts on the client.

C It blocks the database transaction and delays the server response.

D It reduces bundle size.

DevTools: Rails logs and New Relic (or similar APM)

How to check: Check Rails server logs for callback execution time or use APM to profile request breakdown.

What to look for: Long callback durations or increased request time before response indicates performance issues.

Practice

1. What is the main purpose of callbacks in Rails models?

easy

A. To run code automatically at specific points in a model's life

B. To manually call methods from controllers

C. To style the HTML output of views

D. To handle database migrations

Solution

1. Step 1: Understand what callbacks do

   Callbacks are hooks that run code automatically during certain model events like saving or deleting.

2. Step 2: Identify the correct purpose

   Callbacks help automate tasks at specific points in a model's lifecycle, not manual calls or styling.

3. Final Answer:

   To run code automatically at specific points in a model's life -> Option A

4. Quick Check:

   Callbacks = automatic code run [OK]

Hint: Callbacks run code automatically at model events [OK]

Common Mistakes:

• Confusing callbacks with controller methods
• Thinking callbacks style views
• Mixing callbacks with database migrations

2. Which of the following is the correct syntax to define a callback that runs before saving a record?

easy

A. on_save :method_name

B. after_save :method_name

C. before_save do method_name end

D. before_save :method_name

Solution

1. Step 1: Recall callback syntax

   Rails uses before_save :method_name to run a method before saving a record.

2. Step 2: Check other options

   after_save runs after saving, on_save is invalid, and the block syntax is incorrect here.

3. Final Answer:

   before_save :method_name -> Option D

4. Quick Check:

   before_save syntax = before_save :method_name [OK]

Hint: Use before_save :method_name to run code before saving [OK]

Common Mistakes:

• Using after_save instead of before_save
• Trying to use on_save which doesn't exist
• Incorrect block syntax for callbacks

3. Given this model code:

class User < ApplicationRecord
  before_create :set_default_role

  def set_default_role
    self.role ||= 'guest'
  end
end

What will be the role of a new User if none is set before saving?

medium

A. 'guest'

B. 'admin'

C. nil

D. Raises an error

Solution

1. Step 1: Understand before_create callback

   The before_create callback runs the method set_default_role before the record is created in the database.

2. Step 2: Analyze set_default_role method

   The method sets self.role to 'guest' only if it is currently nil or falsey (using ||=).

3. Final Answer:

   'guest' -> Option A

4. Quick Check:

   before_create sets role to 'guest' if none set [OK]

Hint: before_create sets default values if none exist [OK]

Common Mistakes:

• Assuming role stays nil if not set
• Confusing before_create with after_create
• Thinking it raises an error without role

4. Identify the error in this callback definition:

class Post < ApplicationRecord
  before_save :check_title

  def check_title
    if title.blank?
      errors.add(:title, "can't be blank")
      throw :abort
    end
  end
end

medium

A. Using throw :abort is incorrect to stop save

B. No error, this is correct usage

C. Callback method should be private

D. errors.add should be errors.add_error

Solution

1. Step 1: Review callback usage

   The before_save callback runs check_title before saving.

2. Step 2: Check error handling

   Adding errors and using throw :abort is the correct way to stop saving if validation fails.

3. Final Answer:

   No error, this is correct usage -> Option B

4. Quick Check:

   throw :abort stops save correctly [OK]

Hint: Use throw :abort to halt save in callbacks [OK]

Common Mistakes:

• Thinking throw :abort is invalid
• Believing errors.add needs a different method
• Assuming callback methods must be private

5. You want to run a method log_update only after a record is updated but not created. Which callback should you use?

hard

A. before_save

B. after_save

C. after_update

D. before_update

Solution

1. Step 1: Understand callback timing

   after_save runs after both create and update, but after_update runs only after updates.

2. Step 2: Choose callback for updates only

   Since you want to run log_update only after updates, after_update is the correct choice.

3. Final Answer:

   after_update -> Option C

4. Quick Check:

   after_update runs only after updates [OK]

Hint: Use after_update for actions only after updates [OK]

Common Mistakes:

• Using after_save which runs on create too
• Choosing before_update which runs before update
• Confusing before_save with after_update