Queue consumers (processors) in NestJS - Performance & Optimization

Performance: Queue consumers (processors)

MEDIUM IMPACT

This affects how fast queued tasks are processed and how much CPU and memory the server uses during processing.

Processing tasks from a queue efficiently

NestJS

import { Processor, Process } from '@nestjs/bull';
import { Job } from 'bull';

@Processor('email')
export class EmailProcessor {
  @Process()
  async handleEmail(job: Job) {
    await this.sendEmailAsync(job.data);
  }

  async sendEmailAsync(data: any) {
    // non-blocking async email sending
    return new Promise(resolve => setTimeout(() => {
      console.log('Email sent', data);
      resolve(true);
    }, 100));
  }
}

Uses asynchronous non-blocking operations allowing other jobs to be processed concurrently, improving throughput and responsiveness.

📈 Performance GainNon-blocking processing reduces CPU spikes and event loop blocking, enabling smoother job handling.

Processing tasks from a queue efficiently

NestJS

import { Processor, Process } from '@nestjs/bull';
import { Job } from 'bull';

@Processor('email')
export class EmailProcessor {
  @Process()
  async handleEmail(job: Job) {
    // heavy synchronous task
    for (let i = 0; i < 1e8; i++) {
      // blocking loop
    }
    console.log('Email sent', job.data);
  }
}

The consumer runs a heavy synchronous task blocking the event loop, causing delays in processing other jobs and increasing response latency.

📉 Performance CostBlocks event loop during processing, causing high CPU usage and delayed job handling.

Performance Comparison

Pattern	CPU Usage	Event Loop Blocking	Memory Usage	Verdict
Synchronous heavy task	High CPU spike	Blocks event loop	Stable	[X] Bad
Asynchronous non-blocking task	Balanced CPU	No blocking	Stable	[OK] Good
Concurrency = 1	Low CPU utilization	No blocking	Stable	[!] OK
Concurrency > 1	Better CPU utilization	No blocking	Stable	[OK] Good
Growing cache without cleanup	Moderate CPU	No blocking	Memory leak	[X] Bad
No cache or cleared cache	Moderate CPU	No blocking	Stable memory	[OK] Good

Rendering Pipeline

Queue consumers process jobs asynchronously, affecting the Node.js event loop and CPU scheduling. Efficient consumers minimize blocking and allow smooth task handling.

→Event Loop

→CPU Scheduling

→Memory Management

⚠️ BottleneckBlocking synchronous code in consumers causes event loop delays and CPU spikes.

Optimization Tips

1Avoid blocking the event loop with synchronous heavy tasks in consumers.

2Use asynchronous code and control concurrency to improve throughput.

3Prevent memory leaks by avoiding unbounded caches or clearing them regularly.

Performance Quiz - 3 Questions

What is the main performance problem with synchronous heavy tasks in queue consumers?

A They block the event loop causing delays in processing other jobs.

B They reduce memory usage drastically.

C They improve concurrency automatically.

D They reduce CPU usage.

DevTools: Performance

How to check: Record a CPU profile while the queue consumer processes jobs. Look for long tasks blocking the event loop or CPU spikes.

What to look for: Long blocking tasks indicate synchronous code; smooth CPU usage and short tasks indicate good async processing.

Practice

1. What is the main purpose of a queue consumer (processor) in a NestJS application?

easy

A. To send HTTP requests to external APIs

B. To render UI components on the client side

C. To listen to a queue and process jobs asynchronously in the background

D. To manage database migrations synchronously

Solution

1. Step 1: Understand the role of queue consumers

   Queue consumers listen to queues and handle jobs asynchronously, allowing background processing.

2. Step 2: Compare with other options

   Sending HTTP requests, rendering UI, and managing migrations are unrelated to queue consumers.

3. Final Answer:

   To listen to a queue and process jobs asynchronously in the background -> Option C

4. Quick Check:

   Queue consumer = background job handler [OK]

Hint: Queue consumers handle background jobs, not UI or HTTP [OK]

Common Mistakes:

• Confusing queue consumers with HTTP controllers
• Thinking queue consumers run synchronously
• Assuming queue consumers manage UI rendering

2. Which decorator is used to mark a class as a queue consumer (processor) in NestJS?

easy

A. @Processor

B. @Queue

C. @Process

D. @Consumer

Solution

1. Step 1: Identify the decorator for queue consumers

   The @Processor decorator marks a class as a queue consumer in NestJS.

2. Step 2: Differentiate from other decorators

   @Process marks methods, @Queue and @Consumer are not valid NestJS decorators for this purpose.

3. Final Answer:

   @Processor -> Option A

4. Quick Check:

   Class decorator for consumers = @Processor [OK]

Hint: Class decorator for consumers is @Processor, method decorator is @Process [OK]

Common Mistakes:

• Using @Process on the class instead of methods
• Confusing @Processor with @Queue
• Assuming @Consumer is a valid decorator

3. Given the following NestJS queue consumer code, what will be logged when a job with data { name: 'Alice' } is processed?

import { Processor, Process } from '@nestjs/bull';
import { Job } from 'bull';

@Processor('email')
export class EmailProcessor {
  @Process('send')
  async handleSend(job: Job) {
    console.log(`Sending email to ${job.data.name}`);
  }
}

medium

A. No output because handleSend is not called

B. Sending email to Alice

C. Error: job.data is not defined

D. Sending email to undefined

Solution

1. Step 1: Understand job data usage

   The job object contains data with a name property 'Alice'. The method logs this value.

2. Step 2: Confirm method is called on 'send' jobs

   The @Process('send') decorator ensures handleSend runs for jobs named 'send' in the 'email' queue.

3. Final Answer:

   Sending email to Alice -> Option B

4. Quick Check:

   job.data.name = 'Alice' logged correctly [OK]

Hint: Job data is accessed via job.data inside @Process methods [OK]

Common Mistakes:

• Assuming job.data is undefined
• Thinking method won't run without explicit call
• Confusing queue name with job name

4. Identify the error in this NestJS queue consumer code snippet:

import { Processor, Process } from '@nestjs/bull';
import { Job } from 'bull';

@Processor('notifications')
export class NotificationProcessor {
  @Process()
  async handleNotification(job: Job) {
    console.log('Notification:', job.data.message);
  }
}

medium

A. Job parameter type should be any, not Job

B. The class should not have @Processor decorator

C. Console.log syntax is incorrect

D. @Process decorator is missing the job name argument

Solution

1. Step 1: Check @Process decorator usage

   @Process requires a job name string to specify which jobs to handle; it's missing here.

2. Step 2: Validate other parts

   @Processor on class is correct, Job type is valid, console.log syntax is correct.

3. Final Answer:

   @Process decorator is missing the job name argument -> Option D

4. Quick Check:

   @Process needs job name argument [OK]

Hint: @Process must specify job name string inside parentheses [OK]

Common Mistakes:

• Omitting job name in @Process decorator
• Removing @Processor from class
• Changing Job type unnecessarily

5. You want to create a NestJS queue consumer that processes two different job types: 'email' and 'sms' in the same queue 'notifications'. Which is the correct way to define the processor class and methods?

hard

A. Use @Processor('notifications') on class, and two methods with @Process('email') and @Process('sms') decorators

B. Use two separate classes each with @Processor('notifications') and one @Process method

C. Use @Processor('email') and @Processor('sms') on the same class with one @Process method

D. Use @Process('notifications') on methods without @Processor on class

Solution

1. Step 1: Understand queue and job type separation

   The queue is 'notifications'. The job types are 'email' and 'sms'. One class can handle multiple job types with separate @Process decorators.

2. Step 2: Validate correct decorator usage

   @Processor('notifications') marks the queue. Methods use @Process('email') and @Process('sms') to handle each job type.

3. Final Answer:

   Use @Processor('notifications') on class, and two methods with @Process('email') and @Process('sms') decorators -> Option A

4. Quick Check:

   One class, multiple @Process methods for job types [OK]

Hint: One @Processor class can have many @Process methods for different jobs [OK]

Common Mistakes:

• Creating multiple classes for same queue unnecessarily
• Using multiple @Processor decorators on one class
• Omitting @Processor on class and only using @Process