Association callbacks in Ruby on Rails - Performance & Optimization

Performance: Association callbacks

MEDIUM IMPACT

This affects server response time and database transaction speed during object creation or update involving associated records.

Running complex logic inside association callbacks during record save

Ruby on Rails

class Order < ApplicationRecord
  has_many :items
  after_add :enqueue_processing

  def enqueue_processing(item)
    ProcessingJob.perform_later(item.id)
  end
end

Delegates heavy work to background jobs, keeping database transactions fast and responsive.

📈 Performance GainDatabase transaction completes immediately; no blocking delays

Running complex logic inside association callbacks during record save

Ruby on Rails

class Order < ApplicationRecord
  has_many :items
  after_add :heavy_processing

  def heavy_processing(item)
    # complex calculations or external API calls
    sleep(2) # simulating delay
  end
end

Heavy processing inside callbacks blocks the save operation, increasing response time and database lock duration.

📉 Performance CostBlocks database transaction for multiple seconds per added association

Performance Comparison

Pattern	Database Calls	Transaction Blocking	Server Response Time	Verdict
Heavy logic in association callbacks	1+ per callback	Blocks until complete	High latency	[X] Bad
Light callbacks delegating to background jobs	1 minimal call	Non-blocking	Low latency	[OK] Good

Rendering Pipeline

Association callbacks run during ActiveRecord lifecycle events before or after database operations, affecting server processing time but not browser rendering directly.

→Server Processing

→Database Transaction

⚠️ BottleneckDatabase Transaction time increases if callbacks run heavy synchronous code

Optimization Tips

1Keep association callbacks light and fast to avoid blocking database transactions.

2Use background jobs for any heavy or slow processing triggered by callbacks.

3Monitor callback execution time using Rails logs or application performance monitoring tools.

Performance Quiz - 3 Questions

What is the main performance risk of running heavy logic inside association callbacks in Rails?

A It increases CSS paint time.

B It causes browser rendering delays.

C It blocks the database transaction, increasing server response time.

D It reduces client-side JavaScript execution speed.

DevTools: Rails Development Logs and New Relic (or similar APM)

How to check: Enable detailed SQL and callback logging; monitor transaction duration and callback execution time in logs or APM dashboard.

What to look for: Long callback execution times or database transaction durations indicate performance issues.