Pipe performance considerations in Angular

Introduction

Pipes help change how data looks in your app. But if they run too much, your app can slow down. Knowing how to keep pipes fast makes your app smooth and happy.

When you want to format dates or numbers in your app display.

When you need to filter or sort lists shown to users.

When you want to change text style or case before showing it.

When you want to avoid slowing down your app by running heavy calculations repeatedly.

Syntax

Angular

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

@Pipe({
  name: 'examplePipe',
  pure: true // or false
})
export class ExamplePipe implements PipeTransform {
  transform(value: any, ...args: any[]): any {
    // change value here
    const changedValue = value; // example placeholder
    return changedValue;
  }
}

Pure pipes run only when input changes, so they are faster.

Impure pipes run every time change detection runs, which can slow your app.

Examples

This pure pipe changes text to uppercase only when the input text changes.

Angular

@Pipe({ name: 'purePipe', pure: true })
export class PurePipe implements PipeTransform {
  transform(value: string): string {
    return value.toUpperCase();
  }
}

This impure pipe sorts an array but runs on every change detection, which can slow the app if the array is large.

Angular

@Pipe({ name: 'impurePipe', pure: false })
export class ImpurePipe implements PipeTransform {
  transform(value: number[]): number[] {
    return value.slice().sort();
  }
}

Sample Program

This example shows a pure pipe that doubles a number. The pipe runs only when the number changes. Clicking the button increases the number and triggers the pipe again.

Angular

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

@Pipe({
  name: 'double',
  pure: true
})
export class DoublePipe implements PipeTransform {
  transform(value: number): number {
    console.log('DoublePipe transform called');
    return value * 2;
  }
}

@Component({
  selector: 'app-root',
  template: `
    <h1>Number doubled: {{ number | double }}</h1>
    <button (click)="increment()">Increment</button>
  `
})
export class AppComponent {
  number = 1;

  increment() {
    this.number++;
  }
}

Important Notes

Use pure pipes for simple, fast transformations to avoid unnecessary work.

Avoid heavy calculations inside pipes; do them outside if possible.

Impure pipes can cause performance issues because they run very often.

Summary

Pipes change how data looks but can slow your app if used carelessly.

Pure pipes run only when inputs change, making them faster.

Impure pipes run every time Angular checks for changes, so use them sparingly.

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