Web workers for heavy computation in Angular - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when a heavy computation runs inside an Angular web worker?

Consider an Angular app using a web worker to perform a heavy calculation. What is the main benefit of running this computation inside a web worker?

A The computation can directly update Angular component variables without messaging.

B The computation runs faster because web workers use GPU acceleration.

C The web worker automatically caches results to speed up future computations.

D The UI remains responsive because the computation runs on a separate thread.

💡 Hint

Think about how web workers affect the main UI thread.

Web workers run code on a separate thread, so the UI thread is free to stay responsive. They do not speed up computation by GPU or share variables directly.

📝 Syntax

intermediate

Which Angular syntax correctly creates a web worker?

You want to create a web worker in Angular using the CLI. Which command is correct?

A ng generate web-worker my-worker

B ng add web-worker my-worker

C ng create worker my-worker

D ng generate worker my-worker

💡 Hint

The Angular CLI uses 'generate' for scaffolding code.

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

🔧 Debug

advanced

Why does this Angular web worker code fail to update the UI?

Given this Angular component code snippet:

worker.onmessage = ({ data }) => {
  this.result = data;
};

Why might the UI not show the updated result value?

A Because web workers cannot send messages back to the main thread.

B Because the assignment happens outside Angular's zone, change detection is not triggered.

C Because <code>this</code> inside the callback does not refer to the component instance.

D Because <code>result</code> must be updated inside <code>ngOnInit</code> only.

💡 Hint

Angular needs to know when to update the UI after async events.

Web worker callbacks run outside Angular's zone, so Angular does not detect changes automatically. You must run the update inside NgZone.run() or trigger change detection manually.

❓ state_output

advanced

What is the value of result after this Angular web worker message?

In an Angular component, you have:

worker.postMessage(5);
worker.onmessage = ({ data }) => {
  this.result = data * 2;
};

The web worker code is:

addEventListener('message', ({ data }) => {
  postMessage(data + 3);
});

What is the value of result after the message is received?

A 16

B 10

C 8

D 5

💡 Hint

Calculate step-by-step: worker adds 3, then component doubles.

The worker receives 5, adds 3 to get 8, sends 8 back. The component doubles 8 to get 16.

🧠 Conceptual

expert

Why should Angular web workers avoid accessing DOM or Angular services?

Which is the main reason Angular web workers should not access the DOM or Angular services directly?

A Web workers automatically synchronize DOM changes, so manual access is redundant.

B Accessing DOM in web workers causes Angular to crash immediately.

C Web workers run in a separate thread without access to the DOM or Angular's dependency injection.

D Angular services are only available inside web workers, not in the main thread.

💡 Hint

Think about what web workers can and cannot do compared to the main thread.

Web workers run in a separate thread and have no access to the DOM or Angular services. They communicate only via messages.

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