When to use OnPush in Angular - Performance & Optimization

Performance: When to use OnPush

HIGH IMPACT

OnPush affects how Angular detects changes and updates the DOM, impacting rendering speed and responsiveness.

Optimizing change detection for a component with mostly immutable inputs

Angular

import { Component, ChangeDetectionStrategy, Input } from '@angular/core';
@Component({
  selector: 'app-good',
  changeDetection: ChangeDetectionStrategy.OnPush,
  template: `<p>{{data.name}}</p>`
})
export class GoodComponent {
  @Input() data!: { name: string };
}

OnPush runs change detection only when input references change, reducing unnecessary checks.

📈 Performance Gainreduces change detection cycles, improving input responsiveness and lowering reflows

Optimizing change detection for a component with mostly immutable inputs

Angular

import { Component } from '@angular/core';
@Component({
  selector: 'app-bad',
  template: `<p>{{data.name}}</p>`
})
export class BadComponent {
  data = { name: 'Angular' };
}

Default change detection runs on every event and async operation, causing many unnecessary DOM checks.

📉 Performance Costtriggers change detection on every event, causing multiple reflows and slower INP

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Default Change Detection	Runs on all events and async tasks	Multiple reflows per event	Higher paint cost due to frequent updates	[X] Bad
OnPush Change Detection	Runs only on input reference changes or events	Minimal reflows	Lower paint cost with fewer updates	[OK] Good

Rendering Pipeline

OnPush changes when Angular runs change detection, reducing the frequency of style recalculations and layout updates.

→Change Detection

→Layout

→Paint

⚠️ BottleneckChange Detection stage is most expensive when running frequently on many components.

Core Web Vital Affected

INP

OnPush affects how Angular detects changes and updates the DOM, impacting rendering speed and responsiveness.

Optimization Tips

1Use OnPush for components with immutable inputs to reduce change detection frequency.

2Avoid OnPush if your component relies on mutable objects that change internally without new references.

3OnPush improves input responsiveness by minimizing unnecessary DOM updates.

Performance Quiz - 3 Questions

What is the main performance benefit of using OnPush change detection in Angular?

A It disables change detection completely.

B It reduces unnecessary change detection cycles by running only on input changes.

C It forces Angular to check all components more frequently.

D It increases bundle size to improve speed.

DevTools: Performance

How to check: Record a performance profile while interacting with the component. Look for change detection cycles and layout recalculations.

What to look for: Fewer and shorter change detection events and layout recalculations indicate better performance with OnPush.

Practice

1. What is the main reason to use ChangeDetectionStrategy.OnPush in an Angular component?

easy

A. To improve performance by checking for changes only when inputs change or events occur

B. To disable change detection completely

C. To force Angular to check for changes on every event

D. To automatically update the component without any input changes

Solution

1. Step 1: Understand OnPush behavior

   OnPush tells Angular to check for changes only when input properties change or events inside the component happen.

2. Step 2: Compare with other options

   It does not disable change detection or force checks on every event, but optimizes performance by limiting checks.

3. Final Answer:

   To improve performance by checking for changes only when inputs change or events occur -> Option A

4. Quick Check:

   OnPush improves performance = A [OK]

Hint: OnPush triggers checks only on input or event changes [OK]

Common Mistakes:

• Thinking OnPush disables change detection
• Assuming OnPush checks on every event
• Believing OnPush updates without input changes

2. Which of the following is the correct way to set OnPush change detection in an Angular component?

easy

A. @Component({ selector: 'app-example', changeDetection: ChangeDetectionStrategy.Default })

B. @Component({ selector: 'app-example', changeDetection: ChangeDetectionStrategy.OnPush })

C. @Component({ selector: 'app-example', changeDetection: 'OnPush' })

D. @Component({ selector: 'app-example', changeDetection: true })

Solution

1. Step 1: Recall Angular syntax for change detection

   The correct syntax uses the enum ChangeDetectionStrategy.OnPush inside the component decorator.

2. Step 2: Eliminate incorrect options

   A uses Default strategy, B uses a boolean which is invalid, C uses a string instead of enum.

3. Final Answer:

   @Component({ selector: 'app-example', changeDetection: ChangeDetectionStrategy.OnPush }) -> Option B

4. Quick Check:

   Use enum OnPush in decorator = D [OK]

Hint: Use ChangeDetectionStrategy.OnPush enum in @Component [OK]

Common Mistakes:

• Using string 'OnPush' instead of enum
• Setting changeDetection to true or false
• Confusing Default with OnPush

3. Given this component using OnPush:

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

What happens if the parent updates count by mutating an object property instead of replacing the input?

medium

A. The component updates only after a manual change detection call

B. The component updates and shows the new count

C. Angular throws a runtime error

D. The component does not update because OnPush requires immutable input changes

Solution

1. Step 1: Understand OnPush input change detection

   OnPush detects changes only when input references change (immutable updates), not when internal properties mutate.

2. Step 2: Analyze mutation effect

   Mutating an object property keeps the same reference, so Angular does not detect the change and does not update the view.

3. Final Answer:

   The component does not update because OnPush requires immutable input changes -> Option D

4. Quick Check:

   OnPush needs new input references = A [OK]

Hint: OnPush needs new input objects, not mutated ones [OK]

Common Mistakes:

• Assuming mutation triggers update
• Expecting runtime errors on mutation
• Thinking manual detection is always needed

4. You have an Angular component with OnPush strategy but the view does not update after input changes. Which fix will solve this problem?

medium

A. Manually call ChangeDetectorRef.detectChanges() after input mutation

B. Switch to Default change detection strategy

C. Replace the input object with a new reference instead of mutating it

D. Remove the @Input() decorator

Solution

1. Step 1: Identify why view doesn't update

   OnPush requires new input references to detect changes; mutating inputs keeps the same reference, so no update.

2. Step 2: Choose the best fix

   Replacing the input with a new object triggers change detection properly without needing manual calls or strategy changes.

3. Final Answer:

   Replace the input object with a new reference instead of mutating it -> Option C

4. Quick Check:

   New input references trigger OnPush updates = C [OK]

Hint: Use new input objects, not mutations, to update OnPush views [OK]

Common Mistakes:

• Relying on manual detectChanges() calls unnecessarily
• Switching to Default without reason
• Removing @Input() breaks data flow

5. You have a parent component passing a list of items to a child component with OnPush strategy. The parent updates the list by adding a new item using items.push(newItem). The child does not update. How should you fix this to ensure the child updates efficiently?

hard

A. Use items = [...items, newItem] to create a new array reference

B. Call markForCheck() on the child's ChangeDetectorRef after push

C. Change child's strategy to Default

D. Manually trigger detectChanges() in the child after push

Solution

1. Step 1: Understand OnPush and input references

   OnPush detects changes only when input references change, so mutating the array with push keeps the same reference.

2. Step 2: Apply immutable update

   Using items = [...items, newItem] creates a new array reference, triggering OnPush change detection in the child.

3. Final Answer:

   Use items = [...items, newItem] to create a new array reference -> Option A

4. Quick Check:

   Immutable input updates trigger OnPush = B [OK]

Hint: Create new input arrays to trigger OnPush updates [OK]

Common Mistakes:

• Mutating arrays with push expecting updates
• Relying on manual detectChanges() calls
• Changing strategy unnecessarily