Why change detection matters in Angular - Performance Evidence

Performance: Why change detection matters

HIGH IMPACT

Change detection impacts how fast the page updates after user actions or data changes, affecting interaction responsiveness and visual stability.

Updating UI when data changes in Angular

Angular

import { Component, ChangeDetectionStrategy } from '@angular/core';
@Component({
  selector: 'app-root',
  changeDetection: ChangeDetectionStrategy.OnPush,
  template: `<div>{{ counter }}</div><button (click)="increment()">Increment</button>`
})
export class AppComponent {
  counter = 0;
  increment() {
    this.counter++;
  }
}

OnPush strategy limits change detection to only when input properties change or events occur inside the component, reducing unnecessary checks.

📈 Performance Gainreduces change detection runs by up to 90% in large apps, improving input responsiveness

Updating UI when data changes in Angular

Angular

import { Component } from '@angular/core';
@Component({
  selector: 'app-root',
  template: `<div>{{ counter }}</div><button (click)="increment()">Increment</button>`
})
export class AppComponent {
  counter = 0;
  increment() {
    this.counter++;
  }
}

Default change detection runs for the entire component tree on every event, causing many unnecessary checks and DOM updates.

📉 Performance Costtriggers full component tree check on each event, causing slow input responsiveness on large apps

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Default Change Detection	Many unnecessary checks	Multiple reflows per event	High paint cost due to frequent updates	[X] Bad
OnPush Change Detection	Checks only when needed	Single or minimal reflows	Lower paint cost with fewer updates	[OK] Good

Rendering Pipeline

Angular's change detection runs after events or async tasks, checking component data and updating the DOM if needed. Inefficient detection causes excessive Layout and Paint work.

→JavaScript Execution

→Layout

→Paint

⚠️ BottleneckJavaScript Execution during change detection triggers costly Layout and Paint if many DOM updates occur.

Core Web Vital Affected

INP

Change detection impacts how fast the page updates after user actions or data changes, affecting interaction responsiveness and visual stability.

Optimization Tips

1Avoid running change detection on the entire component tree unnecessarily.

2Use OnPush change detection strategy for better performance.

3Keep component inputs immutable to help Angular detect changes efficiently.

Performance Quiz - 3 Questions

What is the main performance problem with Angular's default change detection?

A It never updates the DOM automatically

B It runs checks on the entire component tree on every event

C It only updates components with OnPush strategy

D It blocks network requests during detection

DevTools: Performance

How to check: Record a performance profile while interacting with the app. Look for long scripting tasks labeled 'change detection'.

What to look for: High scripting time during change detection indicates inefficient updates; shorter tasks mean better performance.

Practice

1. Why is change detection important in Angular applications?

easy

A. It updates the user interface when data changes.

B. It compiles the Angular code into JavaScript.

C. It manages routing between pages.

D. It handles HTTP requests automatically.

Solution

1. Step 1: Understand the role of change detection

   Change detection watches for data changes and updates the screen accordingly.

2. Step 2: Compare with other Angular features

   Compiling code, routing, and HTTP handling are separate Angular tasks, not change detection.

3. Final Answer:

   It updates the user interface when data changes. -> Option A

4. Quick Check:

   Change detection = UI updates [OK]

Hint: Change detection means screen updates when data changes [OK]

Common Mistakes:

• Confusing change detection with routing
• Thinking it compiles code
• Assuming it handles HTTP requests

2. Which of the following is the correct way to trigger change detection manually in Angular?

easy

A. this.changeDetectorRef.updateView()

B. this.changeDetectorRef.refresh()

C. this.changeDetectorRef.detectChanges()

D. this.changeDetectorRef.runChange()

Solution

1. Step 1: Recall Angular's ChangeDetectorRef API

   The method to trigger change detection manually is detectChanges().

2. Step 2: Verify method names

   Other options like updateView(), refresh(), or runChange() do not exist in Angular's API.

3. Final Answer:

   this.changeDetectorRef.detectChanges() -> Option C

4. Quick Check:

   Manual trigger method = detectChanges() [OK]

Hint: Use detectChanges() to manually trigger change detection [OK]

Common Mistakes:

• Using non-existent methods like updateView()
• Confusing detectChanges() with refresh()
• Trying to call runChange() which is invalid

3. Consider this Angular component snippet:

export function Counter() {
  const [count, setCount] = useState(0);
  function increment() {
    setCount(count + 1);
  }
  return `Count: ${count}`;
}

What happens if increment() is called but Angular's change detection does not run?

medium

A. The button label stays the same and does not show the updated count.

B. Angular throws a runtime error.

C. The button label updates immediately to show the new count.

D. The component reloads completely.

Solution

1. Step 1: Understand change detection role in UI update

   Change detection updates the screen to reflect data changes like count.

2. Step 2: Analyze effect of no change detection

   If change detection does not run, the UI does not refresh, so the button label stays the same.

3. Final Answer:

   The button label stays the same and does not show the updated count. -> Option A

4. Quick Check:

   No change detection = no UI update [OK]

Hint: Without change detection, UI won't reflect data changes [OK]

Common Mistakes:

• Assuming UI updates automatically without change detection
• Expecting a runtime error
• Thinking component reloads fully

4. You wrote this Angular code:

import { ChangeDetectorRef } from '@angular/core';

@Component({ selector: 'app-test', template: `
{{value}}
` })
export class TestComponent {
  value = 0;
  constructor(private cdr: ChangeDetectorRef) {}
  update() {
    this.value = 1;
    // Missing change detection trigger here
  }
}

Why does the displayed value not update after calling update()?

medium

A. Angular templates cannot display variables.

B. Change detection was not triggered after changing the value.

C. The component selector is incorrect.

D. The value variable is not declared properly.

Solution

1. Step 1: Identify missing change detection trigger

   The update method changes value but does not call detectChanges() or similar.

2. Step 2: Understand Angular's automatic detection limits

   Sometimes Angular does not detect changes automatically, so manual trigger is needed.

3. Final Answer:

   Change detection was not triggered after changing the value. -> Option B

4. Quick Check:

   Missing change detection = no UI update [OK]

Hint: Always trigger change detection after manual data changes [OK]

Common Mistakes:

• Blaming variable declaration
• Thinking selector is wrong
• Assuming templates can't show variables

5. You have a list of user objects and want to display their names in Angular. You update the list by replacing it with a new array but the UI does not refresh. What is the best way to ensure Angular detects the change?

hard

A. Restart the Angular application.

B. Modify the existing array without replacing it.

C. Use setTimeout to delay the update.

D. Manually call changeDetectorRef.detectChanges() after updating the list.

Solution

1. Step 1: Understand Angular's change detection on object references

   Angular detects changes when object references change or manual detection runs.

2. Step 2: Analyze options for updating the list

   Replacing the array changes reference but sometimes Angular needs manual detectChanges() call to update UI immediately.

3. Step 3: Evaluate other options

   Modifying existing array may not trigger detection; setTimeout delays but is unreliable; restarting app is extreme.

4. Final Answer:

   Manually call changeDetectorRef.detectChanges() after updating the list. -> Option D

5. Quick Check:

   Manual detectChanges() ensures UI updates [OK]

Hint: Call detectChanges() after replacing data arrays [OK]

Common Mistakes:

• Modifying array without changing reference
• Using setTimeout as a fix
• Restarting app instead of fixing detection