Queue producers in NestJS - Performance & Optimization

Performance: Queue producers

MEDIUM IMPACT

This affects how fast messages are sent to the queue and how it impacts server responsiveness and resource usage.

Sending messages to a queue without blocking the main thread

NestJS

sendMessage(data) {
  this.queueClient.send(data).subscribe();
  // fire-and-forget, non-blocking
}

Does not wait for confirmation, allowing other tasks to run immediately.

📈 Performance GainNon-blocking send reduces INP delays

Sending messages to a queue without blocking the main thread

NestJS

async sendMessage(data) {
  await this.queueClient.send(data).toPromise();
  // waits for confirmation before continuing
}

Waiting synchronously for the queue to confirm each message blocks the event loop, delaying other tasks.

📉 Performance CostBlocks event loop per message, increasing INP latency

Performance Comparison

Pattern	Event Loop Blocking	Throughput	Resource Usage	Verdict
Synchronous await per message	High (blocks event loop)	Low (sequential)	Moderate	[X] Bad
Fire-and-forget async send	Low (non-blocking)	High (parallel)	Low	[OK] Good

Rendering Pipeline

Queue producer code runs in the Node.js event loop, affecting how quickly the server can handle other requests and tasks.

→Event Loop

→Task Scheduling

→I/O Operations

⚠️ BottleneckBlocking on synchronous waits for queue confirmation delays event loop processing.

Core Web Vital Affected

INP

This affects how fast messages are sent to the queue and how it impacts server responsiveness and resource usage.

Optimization Tips

1Avoid awaiting each queue message send sequentially to prevent event loop blocking.

2Use asynchronous, fire-and-forget sends or batch sends to improve throughput.

3Monitor event loop blocking in Node.js DevTools to detect performance bottlenecks.

Performance Quiz - 3 Questions

What is the main performance problem with awaiting each queue message send sequentially?

A It causes layout shifts in the browser.

B It blocks the event loop, delaying other tasks.

C It increases memory usage significantly.

D It reduces network bandwidth.

DevTools: Node.js Inspector (Chrome DevTools Performance panel)

How to check: Record a performance profile while sending messages; look for long tasks blocking the event loop.

What to look for: Long blocking tasks or gaps in event loop activity indicate synchronous waits harming responsiveness.