Why background processing improves performance in Ruby on Rails - Performance Evidence

Performance: Why background processing improves performance

HIGH IMPACT

Background processing improves page load speed and interaction responsiveness by moving slow tasks off the main request cycle.

Handling slow tasks like sending emails or processing images during a web request

Ruby on Rails

def create
  User.create!(user_params)
  UserMailer.welcome_email.deliver_later
  render :show
end

Email sending is queued to a background job, so the web response returns immediately.

📈 Performance GainPage renders instantly; background job runs asynchronously

Handling slow tasks like sending emails or processing images during a web request

Ruby on Rails

def create
  User.create!(user_params)
  UserMailer.welcome_email.deliver_now
  render :show
end

Sending email synchronously blocks the web request, delaying page load and user interaction.

📉 Performance CostBlocks rendering for 500ms+ depending on email server response

Performance Comparison

Pattern	Server Blocking	Response Time	User Perceived Speed	Verdict
Synchronous processing	Blocks server thread	High (500ms+ delay)	Slow page load and interaction	[X] Bad
Background processing	No blocking	Low (fast response)	Fast page load and interaction	[OK] Good

Rendering Pipeline

When slow tasks run during the request, the server delays sending HTML, increasing LCP and blocking user input. Background jobs move these tasks outside the request cycle, allowing faster HTML delivery and quicker interaction readiness.

→Server Processing

→Network Response

→Browser Rendering

⚠️ BottleneckServer Processing during request

Core Web Vital Affected

LCP, INP

Background processing improves page load speed and interaction responsiveness by moving slow tasks off the main request cycle.

Optimization Tips

1Never run slow tasks like email or image processing during web requests.

2Use background job queues to defer slow work after sending the response.

3Faster server responses improve LCP and INP metrics significantly.

Performance Quiz - 3 Questions

How does moving slow tasks to background jobs affect Largest Contentful Paint (LCP)?

A It improves LCP by reducing server response time

B It worsens LCP by adding extra network requests

C It has no effect on LCP

D It increases layout shifts causing worse CLS

DevTools: Network and Performance panels

How to check: Record a page load in Performance panel; check if main thread is blocked waiting on server response. In Network panel, check response time for main HTML request.

What to look for: Long server response times indicate blocking tasks; fast response with background jobs shows better performance.

Practice

1. Why does background processing improve performance in a Rails application?

easy

A. It runs slow tasks separately, keeping the app responsive.

B. It makes the app use more memory.

C. It delays all tasks until the user logs out.

D. It disables user input during processing.

Solution

1. Step 1: Understand what background processing does

   Background processing runs slow or heavy tasks separately from the main app flow.

2. Step 2: Connect background processing to app responsiveness

   By running tasks separately, the app stays responsive and users don't wait for slow tasks to finish.

3. Final Answer:

   It runs slow tasks separately, keeping the app responsive. -> Option A

4. Quick Check:

   Background processing = keeps app responsive [OK]

Hint: Background jobs run separately to keep app fast [OK]

Common Mistakes:

• Thinking background jobs delay user actions
• Believing background jobs increase memory without benefit
• Confusing background jobs with disabling input

2. Which is the correct way to schedule a background job in Rails?

easy

A. MyJob.perform_later

B. MyJob.perform_now

C. MyJob.run_immediately

D. MyJob.execute_sync

Solution

1. Step 1: Recall Rails background job syntax

   Rails uses perform_later to enqueue jobs for background processing.

2. Step 2: Identify the correct method

   perform_now runs job immediately, not in background; other options are invalid.

3. Final Answer:

   MyJob.perform_later -> Option A

4. Quick Check:

   Schedule background job = perform_later [OK]

Hint: Use perform_later to run jobs in background [OK]

Common Mistakes:

• Using perform_now which runs job immediately
• Using non-existent methods like run_immediately
• Confusing perform_later with synchronous calls

3. Given this Rails code snippet, what will the user experience when MyJob.perform_later is called?

class MyJob < ApplicationJob
  def perform
    sleep 5
    puts 'Job done'
  end
end

MyJob.perform_later

medium

A. The job runs immediately and blocks the app.

B. The job runs in background; user sees page instantly.

C. The user waits 5 seconds before the page loads.

D. The job never runs because of syntax error.

Solution

1. Step 1: Understand perform_later behavior

   Calling perform_later queues the job to run asynchronously in background.

2. Step 2: Analyze user experience

   The user does not wait for the job to finish; the page loads immediately while job runs separately.

3. Final Answer:

   The job runs in background; user sees page instantly. -> Option B

4. Quick Check:

   perform_later = async job, no user wait [OK]

Hint: perform_later runs job async, user not blocked [OK]

Common Mistakes:

• Thinking perform_later blocks user until job finishes
• Confusing perform_later with perform_now
• Assuming syntax error without checking code

4. Identify the error in this Rails background job usage:

class ReportJob < ApplicationJob
  def perform
    generate_report
  end
end

ReportJob.perform_later()

medium

A. Missing parentheses in perform_later call.

B. Background jobs cannot call instance methods.

C. perform_later should not have parentheses when called.

D. No error; code is correct.

Solution

1. Step 1: Check syntax of perform_later call

   Calling perform_later() with or without parentheses is valid Ruby syntax.

2. Step 2: Verify job method usage

   Calling instance method generate_report inside perform is allowed and common.

3. Final Answer:

   No error; code is correct. -> Option D

4. Quick Check:

   perform_later() syntax is valid [OK]

Hint: Parentheses optional in Ruby method calls [OK]

Common Mistakes:

• Thinking parentheses cause error in perform_later
• Believing instance methods can't be called in jobs
• Assuming missing arguments cause error

5. You want to send a welcome email after user signup without making the user wait. Which approach best uses background processing in Rails?

hard

A. Call UserMailer.welcome_email(user).deliver_now inside the signup controller.

B. Send the email synchronously after signup completes.

C. Call UserMailer.welcome_email(user).deliver_later inside the signup controller.

D. Use sleep to delay sending the email.

Solution

1. Step 1: Identify synchronous vs asynchronous email sending

   deliver_now sends email immediately, blocking user; deliver_later queues email to send in background.

2. Step 2: Choose option that avoids user wait

   Using deliver_later sends email asynchronously, so user signup is fast and responsive.

3. Final Answer:

   Call UserMailer.welcome_email(user).deliver_later inside the signup controller. -> Option C

4. Quick Check:

   deliver_later = async email sending [OK]

Hint: Use deliver_later to send emails without delay [OK]

Common Mistakes:

• Using deliver_now which blocks user
• Trying to delay with sleep which blocks app
• Sending email synchronously after signup