Web workers for heavy computation in Angular

Introduction

Web workers let your app do heavy work without freezing the screen. They run tasks in the background so users can keep clicking and typing smoothly.

When you need to process large data sets without slowing down the app interface.

When performing complex calculations that take noticeable time.

When you want to keep animations and user interactions smooth during heavy tasks.

When fetching and processing data from APIs that require extra work before showing.

When you want to offload tasks like image or video processing from the main thread.

Syntax

Angular

ng generate web-worker worker-name

// In your component or service:
const worker = new Worker(new URL('./worker-name.worker.ts', import.meta.url));
worker.postMessage(data);
worker.onmessage = ({ data }) => {
  console.log('Result from worker:', data);
};

Use Angular CLI to generate a web worker file with ng generate web-worker.

Web workers communicate with the main app using postMessage and onmessage.

Examples

This command creates a new web worker file named heavyCalc.worker.ts.

Angular

ng generate web-worker heavyCalc

This code sends a number to the worker and logs the result when the worker sends it back.

Angular

const worker = new Worker(new URL('./heavyCalc.worker.ts', import.meta.url));
worker.postMessage(1000000);
worker.onmessage = ({ data }) => {
  console.log('Sum is', data);
};

The worker listens for messages, does the sum calculation, then sends the result back.

Angular

// heavyCalc.worker.ts
addEventListener('message', ({ data }) => {
  let sum = 0;
  for(let i = 0; i <= data; i++) {
    sum += i;
  }
  postMessage(sum);
});

Sample Program

This Angular component uses a web worker to calculate the sum of numbers from 0 to 1,000,000. When you click the button, the calculation runs in the background. The UI stays responsive, and the result shows when ready.

Angular

import { Component } from '@angular/core';

@Component({
  selector: 'app-root',
  template: `
    <h1>Sum Calculator with Web Worker</h1>
    <button (click)="startCalculation()">Calculate Sum</button>
    <p *ngIf="result !== null">Result: {{ result }}</p>
  `
})
export class AppComponent {
  result: number | null = null;
  worker: Worker | undefined;

  constructor() {
    if (typeof Worker !== 'undefined') {
      this.worker = new Worker(new URL('./sum.worker.ts', import.meta.url));
      this.worker.onmessage = ({ data }) => {
        this.result = data;
      };
    }
  }

  startCalculation() {
    this.result = null;
    this.worker?.postMessage(1000000);
  }
}

// sum.worker.ts
addEventListener('message', ({ data }) => {
  let sum = 0;
  for (let i = 0; i <= data; i++) {
    sum += i;
  }
  postMessage(sum);
});

Important Notes

Web workers cannot access the DOM directly. They only communicate via messages.

Always check if Worker is supported in the browser before creating one.

Keep the worker code simple and focused on heavy tasks to get the best performance.

Summary

Web workers run heavy tasks in the background to keep the app smooth.

Use Angular CLI to create workers easily and communicate with them using messages.

They help improve user experience by preventing UI freezes during big computations.

Practice

1. What is the main purpose of using Web Workers in an Angular application?

easy

A. To style components dynamically

B. To run heavy computations in the background without freezing the UI

C. To handle HTTP requests faster

D. To manage routing between pages

Solution

1. Step 1: Understand what Web Workers do

   Web Workers allow running scripts in background threads separate from the main UI thread.

2. Step 2: Identify the benefit in Angular apps

   This prevents the UI from freezing during heavy computations, improving user experience.

3. Final Answer:

   To run heavy computations in the background without freezing the UI -> Option B

4. Quick Check:

   Web Workers = background heavy tasks [OK]

Hint: Web Workers keep UI smooth by running heavy tasks separately [OK]

Common Mistakes:

• Thinking Web Workers handle UI styling
• Confusing Web Workers with HTTP request handlers
• Assuming Web Workers manage routing

2. Which Angular CLI command correctly creates a new Web Worker named compute?

easy

A. ng new worker compute

B. ng create worker compute

C. ng add worker compute

D. ng generate worker compute

Solution

1. Step 1: Recall Angular CLI syntax for generating workers

   The correct command to generate a worker is ng generate worker <name>.

2. Step 2: Match the command with the options

   Only ng generate worker compute uses the correct syntax: ng generate worker compute.

3. Final Answer:

   ng generate worker compute -> Option D

4. Quick Check:

   Generate worker = ng generate worker [OK]

Hint: Use 'ng generate worker' to create workers in Angular [OK]

Common Mistakes:

• Using 'ng create' instead of 'ng generate'
• Confusing 'ng add' with worker creation
• Trying 'ng new' which creates projects, not workers

3. Given this Angular Web Worker code snippet, what will be logged in the console?

const worker = new Worker(new URL('./compute.worker', import.meta.url));
worker.onmessage = ({ data }) => console.log('Result:', data);
worker.postMessage(10);

Assuming the worker script doubles the input number and sends it back.

medium

A. Result: undefined

B. Result: 10

C. Result: 20

D. Error: Worker not found

Solution

1. Step 1: Understand the message flow

   The main thread sends 10 to the worker using postMessage(10).

2. Step 2: Worker doubles the input and sends back

   The worker processes 10, doubles it to 20, and sends it back via postMessage.

3. Step 3: Main thread logs the received data

   The onmessage handler logs 'Result: 20'.

4. Final Answer:

   Result: 20 -> Option C

5. Quick Check:

   Input 10 doubled = 20 [OK]

Hint: Worker doubles input, so output is input x 2 [OK]

Common Mistakes:

• Assuming worker returns input unchanged
• Expecting undefined because of async timing
• Thinking worker script is missing causing error

4. What is the main error in this Angular Web Worker usage?

const worker = new Worker('./compute.worker');
worker.onmessage = (event) => console.log(event.data);
worker.postMessage(5);

medium

A. Missing import.meta.url in Worker URL

B. postMessage should be called before onmessage

C. Worker script path should be absolute URL

D. onmessage handler must be async function

Solution

1. Step 1: Check how the Worker is created

   In Angular, the worker URL must use new URL('./compute.worker', import.meta.url) for correct bundling.

2. Step 2: Identify the missing part

   The code uses a plain string './compute.worker' which causes a runtime error because the path is unresolved.

3. Final Answer:

   Missing import.meta.url in Worker URL -> Option A

4. Quick Check:

   Worker URL needs import.meta.url [OK]

Hint: Always use new URL(path, import.meta.url) for worker paths [OK]

Common Mistakes:

• Calling postMessage before setting onmessage
• Using absolute URL instead of relative with import.meta.url
• Making onmessage async unnecessarily

5. You want to perform a heavy calculation on a large array without freezing the UI. Which approach best uses Angular Web Workers to achieve this?

1. Create a worker with Angular CLI.
2. Send the large array to the worker using postMessage.
3. In the worker, process the array and send back the result.
4. Update the UI with the result when received.

What is the best practice to handle the large data transfer efficiently?

hard

A. Use Transferable Objects like ArrayBuffer to avoid copying data

B. Send data as JSON strings to simplify parsing

C. Split the array into small chunks and send each separately

D. Process the array on the main thread to avoid messaging overhead

Solution

1. Step 1: Understand data transfer in Web Workers

   Sending large data copies it by default, which can be slow and freeze UI.

2. Step 2: Use Transferable Objects to optimize

   Transferable Objects like ArrayBuffer transfer ownership without copying, making communication efficient.

3. Step 3: Compare options

   Sending JSON strings adds parsing overhead, splitting chunks adds complexity, and processing on main thread blocks UI.

4. Final Answer:

   Use Transferable Objects like ArrayBuffer to avoid copying data -> Option A

5. Quick Check:

   Transferable Objects = efficient large data transfer [OK]

Hint: Transfer large data with Transferable Objects to avoid UI freeze [OK]

Common Mistakes:

• Sending large data as JSON causing slow parsing
• Splitting data unnecessarily increasing complexity
• Processing heavy tasks on main thread causing freezes