Pipe performance considerations in Angular - Step-by-Step Execution

Concept Flow - Pipe performance considerations

Component Template Uses Pipe

↓

Angular Detects Change

↓

Pipe Transform Called?

↓

Pipe Executes

↓

Output Rendered

Angular checks if a pipe needs to run on change detection. Pure pipes run only if inputs change; impure pipes run every time.

Execution Sample

Angular

import { Pipe, PipeTransform } from '@angular/core';

@Pipe({ name: 'example', pure: true })
export class ExamplePipe implements PipeTransform {
  transform(value: string): string {
    console.log('Pipe executed');
    return value.toUpperCase();
  }
}

A pure pipe that converts text to uppercase and logs when it runs.

Execution Table

Step	Change Detection Trigger	Pipe Input	Pipe Called?	Action	Output
1	Initial render	'hello'	Yes	Pipe executes, logs 'Pipe executed'	'HELLO'
2	No input change	'hello'	No	Cached result used, no log	'HELLO'
3	Input changes	'world'	Yes	Pipe executes, logs 'Pipe executed'	'WORLD'
4	No input change	'world'	No	Cached result used, no log	'WORLD'
5	Impure pipe example	'test'	Yes	Pipe executes every time, logs 'Pipe executed'	'TEST'
6	Impure pipe example	'test'	Yes	Pipe executes again, logs 'Pipe executed'	'TEST'

💡 Pure pipe skips execution when input unchanged; impure pipe runs every change detection cycle.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6
pipeInput	undefined	'hello'	'hello'	'world'	'world'	'test'	'test'
pipeCalled	false	true	false	true	false	true	true
pipeOutput	undefined	'HELLO'	'HELLO'	'WORLD'	'WORLD'	'TEST'	'TEST'

Key Moments - 3 Insights

Why doesn't the pure pipe run on every change detection cycle?

Because pure pipes run only when their input changes, as shown in steps 2 and 4 where the input is the same and the pipe is not called.

What happens if a pipe is marked as impure?

Impure pipes run every change detection cycle regardless of input changes, as shown in steps 5 and 6 where the pipe executes repeatedly.

How does Angular improve performance with pure pipes?

Angular caches the output of pure pipes and reuses it if the input hasn't changed, avoiding unnecessary pipe executions.

Visual Quiz - 3 Questions

Look at the execution table, at which step does the pipe first skip execution due to unchanged input?

A Step 4

B Step 3

C Step 2

D Step 5

💡 Hint

Check the 'Pipe Called?' column for the first 'No' after initial execution.

According to the variable tracker, what is the pipeOutput after step 3?

A 'WORLD'

B 'HELLO'

C 'test'

D undefined

💡 Hint

Look at the 'pipeOutput' row under 'After Step 3' column.

If the pipe was impure from the start, how would the 'Pipe Called?' column change at step 2?

A It would be 'No'

B It would be 'Yes'

C It would be 'Maybe'

D It would be empty

💡 Hint

Impure pipes run every change detection cycle regardless of input.

Concept Snapshot

Angular pipes transform data in templates.
Pure pipes run only when inputs change, improving performance.
Impure pipes run every change detection cycle.
Use pure pipes for expensive operations.
Angular caches pure pipe results to avoid reruns.
Impure pipes should be used sparingly.

Full Transcript

In Angular, pipes transform data in templates. Pure pipes run only when their input changes, so Angular caches their output and skips running them if inputs are the same. This improves performance by avoiding unnecessary work. Impure pipes run every change detection cycle regardless of input changes, which can slow down the app. The example pipe converts text to uppercase and logs when it runs. On initial render, the pipe runs and logs. On subsequent renders with the same input, the pipe does not run and uses cached output. When input changes, the pipe runs again. Impure pipes run every time, even if input is unchanged. Understanding this helps write efficient Angular apps.

Practice

1. What is the main advantage of using a pure pipe in Angular?

easy

A. It runs on every change detection cycle, ensuring fresh data.

B. It runs only when its input changes, improving performance.

C. It automatically caches data on the server.

D. It allows direct DOM manipulation inside the pipe.

Solution

1. Step 1: Understand pure pipe behavior

   Pure pipes execute only when their input values change, avoiding unnecessary recalculations.

2. Step 2: Compare with impure pipes

   Impure pipes run on every change detection, which can slow the app. Pure pipes avoid this.

3. Final Answer:

   It runs only when its input changes, improving performance. -> Option B

4. Quick Check:

   Pure pipe = runs on input change only [OK]

Hint: Pure pipes run less often, so they boost speed [OK]

Common Mistakes:

• Thinking pure pipes run every change detection
• Confusing pure pipes with caching mechanisms
• Assuming pipes manipulate the DOM directly

2. Which of the following is the correct syntax to explicitly declare a pure pipe in Angular?

easy

A. @Pipe({name: 'examplePipe'}) export class ExamplePipe {}

B. @Pipe({name: 'examplePipe', pure: false}) export class ExamplePipe {}

C. @Pipe({name: 'examplePipe', pure: true}) export class ExamplePipe {}

D. @Pipe({name: 'examplePipe', impure: true}) export class ExamplePipe {}

Solution

1. Step 1: Recall pipe decorator syntax

   The @Pipe decorator accepts a 'pure' boolean property to specify pipe purity.

2. Step 2: Identify correct pure pipe declaration

   Setting pure: true declares a pure pipe. If omitted, pure defaults to true.

3. Final Answer:

   @Pipe({name: 'examplePipe', pure: true}) export class ExamplePipe {} -> Option C

4. Quick Check:

   pure: true means pure pipe [OK]

Hint: Use pure: true or omit it for pure pipes [OK]

Common Mistakes:

• Using 'impure' instead of 'pure' property
• Setting pure: false for pure pipes
• Confusing pure with impure pipe syntax

3. Given this Angular pipe usage:

{{ items | customPipe }}

Assuming customPipe is impure, what happens when Angular runs change detection but items array reference does not change?

medium

A. The pipe does not run because input reference is unchanged.

B. The pipe runs only once and caches the result.

C. Angular throws an error due to impure pipe usage.

D. The pipe runs again and recalculates output every time.

Solution

1. Step 1: Understand impure pipe behavior

   Impure pipes run on every change detection cycle regardless of input changes.

2. Step 2: Analyze effect of unchanged input reference

   Even if the input reference stays the same, impure pipes recalculate output every time.

3. Final Answer:

   The pipe runs again and recalculates output every time. -> Option D

4. Quick Check:

   Impure pipe = runs every change detection [OK]

Hint: Impure pipes run every time, ignoring input changes [OK]

Common Mistakes:

• Assuming impure pipes cache results
• Believing input reference must change for pipe to run
• Thinking Angular errors on impure pipes

4. You have a custom pipe marked as pure, but it still recalculates on every change detection. What is the most likely cause?

medium

A. The pipe input is a new object or array instance each time.

B. The pipe is missing the @Pipe decorator.

C. Angular does not support pure pipes.

D. The pipe class is not exported.

Solution

1. Step 1: Recall pure pipe trigger condition

   Pure pipes run only when their input reference changes.

2. Step 2: Identify cause of repeated recalculation

   If the input is a new object or array instance each time, the reference changes, triggering the pipe.

3. Final Answer:

   The pipe input is a new object or array instance each time. -> Option A

4. Quick Check:

   New input reference triggers pure pipe [OK]

Hint: Check if input object/array is recreated each time [OK]

Common Mistakes:

• Assuming pure pipes run without input changes
• Thinking missing decorator causes recalculation
• Believing Angular lacks pure pipe support

5. You want to optimize an Angular app that uses a pipe to filter a large list. The pipe is impure and slows the app. Which approach best improves performance?

hard

A. Convert the pipe to pure and ensure the input list reference changes only when data updates.

B. Keep the pipe impure but add console logs inside it.

C. Remove the pipe and filter the list directly in the template.

D. Use an impure pipe but call detectChanges() manually after filtering.

Solution

1. Step 1: Identify performance issue with impure pipe

   Impure pipes run every change detection, causing slowdowns with large lists.

2. Step 2: Apply optimization by using pure pipe

   Pure pipes run only when input changes. Changing input reference only on data update avoids unnecessary runs.

3. Final Answer:

   Convert the pipe to pure and ensure the input list reference changes only when data updates. -> Option A

4. Quick Check:

   Pure pipe + stable input reference = better performance [OK]

Hint: Make pipe pure and update input reference only on data change [OK]

Common Mistakes:

• Adding logs does not improve performance
• Filtering in template causes repeated recalculations
• Manually calling detectChanges() won't fix pipe slowness