Job priorities and queues in Ruby on Rails - Performance & Optimization

Performance: Job priorities and queues

MEDIUM IMPACT

This affects how background jobs are processed, impacting response time and server load distribution.

Processing background jobs without priority

Ruby on Rails

class HardJob < ApplicationJob
  queue_as :hard
  def perform(*args)
    # long running task
  end
end

class SoftJob < ApplicationJob
  queue_as :soft
  def perform(*args)
    # quick task
  end
end

# Configure workers to prioritize 'soft' queue over 'hard' queue

Separates jobs by priority queues so quick tasks run first, reducing wait time for important jobs.

📈 Performance GainImproves INP by processing high priority jobs faster, reducing user-perceived delays.

Processing background jobs without priority

Ruby on Rails

class HardJob < ApplicationJob
  queue_as :default
  def perform(*args)
    # long running task
  end
end

class SoftJob < ApplicationJob
  queue_as :default
  def perform(*args)
    # quick task
  end
end

All jobs share the same queue, causing important or quick jobs to wait behind long tasks.

📉 Performance CostDelays critical job processing, increasing INP and user wait times.

Performance Comparison

Pattern	Queue Usage	Job Processing Delay	Server Load Distribution	Verdict
Single default queue	One queue for all jobs	High delay for important jobs	Uneven, long tasks block others	[X] Bad
Multiple prioritized queues	Separate queues by priority	Low delay for high priority jobs	Balanced load, faster critical job processing	[OK] Good

Rendering Pipeline

Job queues run outside the browser but affect user experience by controlling server response timing and interaction readiness.

→Job Scheduling

→Job Execution

→Server Response

⚠️ BottleneckJob Execution when long tasks block shared queues

Core Web Vital Affected

INP

This affects how background jobs are processed, impacting response time and server load distribution.

Optimization Tips

1Separate background jobs into multiple queues by priority to reduce delays.

2Configure workers to process high priority queues first for better responsiveness.

3Avoid mixing long-running and quick jobs in the same queue to prevent blocking.

Performance Quiz - 3 Questions

What is the main performance benefit of using multiple job queues with priorities in Rails?

A It reduces the total number of jobs created.

B All jobs run simultaneously, increasing CPU usage.

C Important jobs get processed faster, improving user interaction responsiveness.

D It eliminates the need for background workers.

DevTools: Rails Sidekiq Web UI or equivalent

How to check: Open the Sidekiq Web UI, monitor queue sizes and job wait times per queue, check if high priority queues are processed faster.

What to look for: Shorter wait times and smaller backlog in high priority queues indicate good performance.

Practice

1. What is the main purpose of setting different job priorities in Rails Active Job?

easy

A. To run more important tasks before less important ones

B. To make jobs run slower

C. To delete jobs automatically

D. To run all jobs at the same time

Solution

1. Step 1: Understand job priorities concept

   Job priorities help decide which jobs run first based on importance.

2. Step 2: Identify the purpose in Rails

   Rails uses priorities to run important jobs before less important ones.

3. Final Answer:

   To run more important tasks before less important ones -> Option A

4. Quick Check:

   Job priorities = run important jobs first [OK]

Hint: Priorities mean important jobs run before others [OK]

Common Mistakes:

• Thinking priorities slow down jobs
• Assuming priorities delete jobs
• Believing all jobs run simultaneously

2. Which syntax correctly sets a queue name for a job class in Rails?

easy

A. queue_as :default

B. queue = :default

C. set_queue :default

D. queue_name = 'default'

Solution

1. Step 1: Recall Rails Active Job syntax

   Rails uses queue_as to set the queue name inside job classes.

2. Step 2: Match correct syntax

   queue_as :default is the correct way to assign the queue.

3. Final Answer:

   queue_as :default -> Option A

4. Quick Check:

   Use queue_as to set queue [OK]

Hint: Use queue_as :name inside job class [OK]

Common Mistakes:

• Using assignment (=) instead of queue_as
• Trying to set queue with unknown methods
• Using string instead of symbol incorrectly

3. Given this job class:

class EmailJob < ApplicationJob
  queue_as :mailers
  def perform(user_id)
    # send email
  end
end

Which queue will this job be added to when enqueued?

medium

A. jobs

B. default

C. emails

D. mailers

Solution

1. Step 1: Check the queue_as setting in the job class

   The job class sets queue_as :mailers, so it uses the 'mailers' queue.

2. Step 2: Understand enqueue behavior

   When enqueued, the job goes to the queue named 'mailers'.

3. Final Answer:

   mailers -> Option D

4. Quick Check:

   queue_as :mailers means queue is 'mailers' [OK]

Hint: queue_as sets the queue name exactly [OK]

Common Mistakes:

• Assuming default queue if queue_as is set
• Confusing queue name with job class name
• Picking similar sounding queue names

4. Identify the error in this job class:

class CleanupJob < ApplicationJob
  queue_as = :low_priority
  def perform
    # cleanup code
  end
end

medium

A. Job class must inherit from ActiveJob::Base

B. perform method must have an argument

C. queue_as should be called as a method, not assigned

D. queue_as must be a string, not a symbol

Solution

1. Step 1: Check how queue_as is set

   queue_as is a method call, not an assignment. Using '=' causes syntax error.

2. Step 2: Correct syntax for queue_as

   It should be queue_as :low_priority without '='.

3. Final Answer:

   queue_as should be called as a method, not assigned -> Option C

4. Quick Check:

   queue_as is a method call, not variable assignment [OK]

Hint: Use queue_as :name, not queue_as = :name [OK]

Common Mistakes:

• Using '=' with queue_as
• Forgetting to inherit from ApplicationJob
• Thinking perform must have arguments always

5. You want to run urgent jobs before normal jobs in Rails. You have two job classes:

class UrgentJob < ApplicationJob
  queue_as :urgent
  def perform
    # urgent task
  end
end

class NormalJob < ApplicationJob
  queue_as :normal
  def perform
    # normal task
  end
end

How can you ensure urgent jobs run before normal jobs when using Sidekiq?

hard

A. Rename UrgentJob to NormalJob

B. Configure Sidekiq to process the 'urgent' queue before the 'normal' queue

C. Set both jobs to the same queue

D. Run urgent jobs manually without Sidekiq

Solution

1. Step 1: Understand queue priority in Sidekiq

   Sidekiq processes queues in the order they are listed in its configuration.

2. Step 2: Set Sidekiq to prioritize 'urgent' queue

   Configure Sidekiq to check the 'urgent' queue before 'normal' to run urgent jobs first.

3. Final Answer:

   Configure Sidekiq to process the 'urgent' queue before the 'normal' queue -> Option B

4. Quick Check:

   Sidekiq queue order controls job priority [OK]

Hint: Set queue order in Sidekiq config for priority [OK]

Common Mistakes:

• Assuming queue_as alone controls priority
• Renaming job classes does not affect queue order
• Running urgent jobs manually is inefficient