Performance impact of change detection in Angular - Performance & Optimization

Performance: Performance impact of change detection

HIGH IMPACT

Change detection affects how quickly Angular updates the UI after data changes, impacting interaction responsiveness and rendering speed.

Updating UI with many components on each data change

Angular

import { Component, ChangeDetectionStrategy } from '@angular/core';
@Component({
  selector: 'app-root',
  changeDetection: ChangeDetectionStrategy.OnPush,
  template: `<child-comp *ngFor="let item of items" [data]="item"></child-comp>`
})
export class AppComponent {
  items = Array(1000).fill(0).map((_, i) => i);
  update() {
    this.items = this.items.map(x => x + 1);
  }
}

Using OnPush strategy limits change detection to components with changed inputs, reducing unnecessary checks.

📈 Performance Gainreduces change detection cycles by 90%+, improving update speed and UI responsiveness

Updating UI with many components on each data change

Angular

import { Component } from '@angular/core';
@Component({
  selector: 'app-root',
  template: `<child-comp *ngFor="let item of items" [data]="item"></child-comp>`
})
export class AppComponent {
  items = Array(1000).fill(0).map((_, i) => i);
  update() {
    this.items = this.items.map(x => x + 1);
  }
}

Angular runs change detection on all components every time 'update' is called, causing many checks and slow UI updates.

📉 Performance Costtriggers 1000+ change detection cycles per update, blocking UI for 100+ ms on slow devices

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Default change detection with many components	Many checks on all components	Multiple reflows if DOM updates	High paint cost due to frequent updates	[X] Bad
OnPush change detection with immutable inputs	Checks only changed components	Minimal reflows	Lower paint cost	[OK] Good

Rendering Pipeline

Angular's change detection runs after events or async tasks, checking component data and updating the DOM if needed.

→Change Detection

→Layout

→Paint

⚠️ BottleneckChange Detection stage is most expensive when many components are checked unnecessarily.

Core Web Vital Affected

INP

Change detection affects how quickly Angular updates the UI after data changes, impacting interaction responsiveness and rendering speed.

Optimization Tips

1Use OnPush change detection to limit checks to components with changed inputs.

2Avoid mutating objects or arrays directly; use immutable patterns to trigger OnPush updates.

3Minimize the number of components checked by change detection to improve interaction speed.

Performance Quiz - 3 Questions

What is the main performance problem with Angular's default change detection on large component trees?

A It only updates the DOM once per second.

B It skips checking components, causing stale UI data.

C It runs change detection on all components every update, causing slow UI response.

D It blocks network requests during change detection.

DevTools: Performance

How to check: Record a performance profile while triggering UI updates. Look for long 'Change Detection' tasks and many component checks.

What to look for: High time spent in 'Change Detection' indicates performance issues; fewer and shorter tasks show better performance.

Practice

1. What is the main purpose of Angular's change detection?

easy

A. To manage routing between pages

B. To compile TypeScript code

C. To handle user authentication

D. To update the view when data changes

Solution

1. Step 1: Understand change detection role

   Change detection in Angular watches for data changes to update the screen accordingly.

2. Step 2: Identify the correct purpose

   Updating the view when data changes matches the role of change detection.

3. Final Answer:

   To update the view when data changes -> Option D

4. Quick Check:

   Change detection updates view [OK]

Hint: Change detection updates the screen on data change [OK]

Common Mistakes:

• Confusing change detection with routing
• Thinking it compiles code
• Mixing it with authentication

2. Which syntax correctly sets the change detection strategy to OnPush in an Angular component?

easy

A. @Component({ detectionStrategy: OnPush })

B. @Component({ changeDetection: ChangeDetectionStrategy.Default })

C. @Component({ changeDetection: ChangeDetectionStrategy.OnPush })

D. @Component({ changeDetectionStrategy: 'OnPush' })

Solution

1. Step 1: Recall correct property name

   The property to set change detection is 'changeDetection' inside @Component decorator.

2. Step 2: Use correct enum value

   The enum value for OnPush is ChangeDetectionStrategy.OnPush, not a string or other property name.

3. Final Answer:

   @Component({ changeDetection: ChangeDetectionStrategy.OnPush }) -> Option C

4. Quick Check:

   Use changeDetection with ChangeDetectionStrategy.OnPush [OK]

Hint: Use changeDetection: ChangeDetectionStrategy.OnPush exactly [OK]

Common Mistakes:

• Using wrong property name like detectionStrategy
• Passing 'OnPush' as string
• Confusing Default with OnPush

3. Given this Angular component with OnPush strategy:

  @Component({
    selector: 'app-counter',
    template: `{{ counter }}`,
    changeDetection: ChangeDetectionStrategy.OnPush
  })
  export class CounterComponent {
    @Input() counter = 0;
  }

What happens if the parent updates counter by setting the same number value again?

medium

A. The component view updates because input changed

B. The component view does not update because value is unchanged

C. Angular throws an error due to OnPush

D. The component view updates only after manual detectChanges call

Solution

1. Step 1: Understand OnPush behavior with inputs

   OnPush triggers change detection only if input references change or events occur.

2. Step 2: Same primitive value means no change

   Setting the same number value again does not change the input reference or value.

3. Final Answer:

   The component view does not update because value is unchanged -> Option B

4. Quick Check:

   OnPush skips unchanged input values [OK]

Hint: OnPush skips updates if input value unchanged [OK]

Common Mistakes:

• Assuming view always updates on input set
• Thinking OnPush causes errors
• Believing manual detectChanges is always needed

4. You have an Angular component using Default change detection. The component updates slowly. Which fix improves performance?

medium

A. Switch to OnPush change detection strategy

B. Remove all @Input properties

C. Use setTimeout to delay updates

D. Disable change detection entirely

Solution

1. Step 1: Identify performance issue cause

   Default strategy checks all components frequently, which can slow large apps.

2. Step 2: Apply OnPush to reduce checks

   OnPush limits checks to when inputs change or events happen, improving speed.

3. Final Answer:

   Switch to OnPush change detection strategy -> Option A

4. Quick Check:

   OnPush improves performance by fewer checks [OK]

Hint: Use OnPush to reduce unnecessary checks [OK]

Common Mistakes:

• Removing inputs breaks data flow
• Using setTimeout doesn't fix detection speed
• Disabling detection breaks UI updates

5. In a large Angular app, you want to optimize change detection. You have a parent component with Default strategy and a child with OnPush. The parent updates a complex object property but mutates it instead of replacing it. What is the impact on the child component's view update?

hard

A. Child view does not update because OnPush checks object reference

B. Child view updates because parent changed object property

C. Child view updates only if detectChanges is called manually

D. Child view updates automatically regardless of mutation

Solution

1. Step 1: Understand OnPush and object mutation

   OnPush triggers on input reference changes, not internal mutations.

2. Step 2: Mutation keeps same object reference

   Mutating object property does not change the reference, so OnPush skips update.

3. Step 3: Child view remains unchanged without manual trigger

   Without new reference or manual detection, child view won't update.

4. Final Answer:

   Child view does not update because OnPush checks object reference -> Option A

5. Quick Check:

   OnPush needs new object reference to update [OK]

Hint: OnPush tracks object references, not internal mutations [OK]

Common Mistakes:

• Assuming mutation triggers update
• Thinking child updates automatically
• Forgetting manual detectChanges option