Web workers for heavy computation in Angular - Step-by-Step Execution

Concept Flow - Web workers for heavy computation

Main Thread starts task

↓

Create Web Worker

↓

Send data to Worker

↓

Worker runs heavy computation

↓

Worker sends result back

↓

Main Thread receives result

↓

Update UI with result

↓

End

The main thread creates a web worker to run heavy tasks separately, sends data to it, waits for the result, then updates the UI without freezing.

Execution Sample

Angular

const worker = new Worker('worker.js');
worker.postMessage(data);
worker.onmessage = ({ data }) => {
  this.result = data;
};

Main thread creates a worker, sends data, and listens for the result to update the UI.

Execution Table

Step	Action	Main Thread State	Worker State	Message Passing	UI Update
1	Create Worker	Worker created, ready	Idle	No message yet	UI unchanged
2	Send data to Worker	Data sent to worker	Receives data	Main -> Worker: data	UI unchanged
3	Worker computes	Waiting for result	Computing heavy task	No message	UI unchanged
4	Worker sends result	Waiting for message	Sends result	Worker -> Main: result	UI unchanged
5	Main receives result	Result received	Idle	No message	UI updated with result
6	End	Task complete	Idle	No message	UI shows final result

💡 Execution stops after main thread receives result and updates UI

Variable Tracker

Variable	Start	After Step 2	After Step 4	Final
worker	undefined	Worker instance	Worker instance	Worker instance
data	input data	Sent to worker	Sent to worker	Sent to worker
result	undefined	undefined	Computed result	Computed result
UI state	Initial	Initial	Initial	Updated with result

Key Moments - 3 Insights

Why doesn't the UI freeze during heavy computation?

Because the heavy computation runs inside the web worker (see Step 3 in execution_table), the main thread stays free to update the UI.

How does the main thread get the result from the worker?

The worker sends a message back (Step 4), and the main thread listens with onmessage to receive it (Step 5).

What happens if the worker is not created properly?

The main thread cannot offload the task, so heavy computation blocks UI (not shown in table but implied at Step 1).

Visual Quiz - 3 Questions

Look at the execution_table, what is the worker state at Step 3?

A Idle

B Computing heavy task

C Sending result

D Waiting for data

💡 Hint

Check the 'Worker State' column at Step 3 in execution_table

At which step does the main thread update the UI?

A Step 5

B Step 3

C Step 2

D Step 1

💡 Hint

Look at the 'UI Update' column in execution_table

If the worker never sends a message back, what happens to the main thread state after Step 4?

A Result received

B Worker instance destroyed

C Waiting for result

D UI updated

💡 Hint

Refer to 'Main Thread State' at Step 4 in execution_table

Concept Snapshot

Web workers run heavy tasks in background threads.
Main thread creates worker and sends data.
Worker computes and sends result back.
Main thread updates UI on receiving result.
Prevents UI freezing during heavy computation.

Full Transcript

Web workers allow Angular apps to run heavy computations without freezing the user interface. The main thread creates a worker and sends data to it. The worker runs the heavy task separately and sends the result back. The main thread listens for this result and updates the UI accordingly. This keeps the app responsive and smooth for users.

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