Why lifecycle hooks matter in Angular - Performance Evidence

Performance: Why lifecycle hooks matter

MEDIUM IMPACT

Lifecycle hooks affect how and when Angular components update, impacting rendering speed and responsiveness.

Running heavy logic on every change detection cycle

Angular

ngOnChanges(changes) {
  if (changes['inputData']) {
    this.calculateSomethingExpensive();
  }
}

Runs heavy logic only when relevant inputs change, reducing unnecessary work.

📈 Performance Gainreduces blocking time to under 10 ms per update

Running heavy logic on every change detection cycle

Angular

ngDoCheck() {
  // heavy computation or DOM manipulation here
  this.calculateSomethingExpensive();
}

Triggers expensive operations on every change detection, causing slow UI updates and janky interactions.

📉 Performance Costblocks rendering for 50+ ms per change detection cycle

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Heavy logic in ngDoCheck	Many unnecessary DOM reads/writes	Multiple reflows per cycle	High paint cost due to layout thrashing	[X] Bad
Conditional logic in ngOnChanges	Minimal DOM operations only on input change	Single reflow when needed	Low paint cost	[OK] Good

Rendering Pipeline

Angular lifecycle hooks run during the change detection phase, which triggers style recalculations, layout, and paint if the DOM changes.

→Change Detection

→Style Calculation

→Layout

→Paint

⚠️ BottleneckChange Detection phase when heavy logic runs unnecessarily

Core Web Vital Affected

INP

Lifecycle hooks affect how and when Angular components update, impacting rendering speed and responsiveness.

Optimization Tips

1Avoid heavy computations in ngDoCheck to prevent slow change detection.

2Use ngOnChanges to run logic only when inputs change.

3Keep lifecycle hook work minimal to maintain smooth UI responsiveness.

Performance Quiz - 3 Questions

Which lifecycle hook should you use to run code only when input properties change?

A ngAfterViewInit

B ngOnChanges

C ngDoCheck

D ngOnDestroy

DevTools: Performance

How to check: Record a performance profile while interacting with the component. Look for long tasks during change detection phases.

What to look for: Long scripting times and repeated layout recalculations indicate inefficient lifecycle hook usage.

Practice

1. Why are lifecycle hooks important in Angular components?

easy

A. They make components load faster by default.

B. They automatically style your components.

C. They replace the need for services.

D. They let you run code at specific times during a component's life.

Solution

1. Step 1: Understand what lifecycle hooks do

   Lifecycle hooks allow you to run code at key moments like creation, update, or destruction of a component.

2. Step 2: Identify the main benefit

   This helps manage resources and keep the app efficient by running code only when needed.

3. Final Answer:

   They let you run code at specific times during a component's life. -> Option D

4. Quick Check:

   Lifecycle hooks = run code at key moments [OK]

Hint: Lifecycle hooks run code at key moments [OK]

Common Mistakes:

• Thinking lifecycle hooks style components
• Believing hooks replace services
• Assuming hooks speed up loading automatically

2. Which of the following is the correct syntax to implement the ngOnInit lifecycle hook in an Angular component?

easy

A. ngOnInit() { console.log('Init'); }

B. onInit() { console.log('Init'); }

C. nginit() { console.log('Init'); }

D. init() { console.log('Init'); }

Solution

1. Step 1: Recall the exact lifecycle hook name

   The correct lifecycle hook method name is ngOnInit with exact casing.

2. Step 2: Match the syntax

   The method should be declared as ngOnInit() { ... } inside the component class.

3. Final Answer:

   ngOnInit() { console.log('Init'); } -> Option A

4. Quick Check:

   Correct hook name and syntax = ngOnInit() { console.log('Init'); } [OK]

Hint: Lifecycle hooks start with 'ng' and use camelCase [OK]

Common Mistakes:

• Using wrong method names like onInit or init
• Incorrect casing like nginit
• Missing 'ng' prefix in method name

3. Given this Angular component code snippet, what will be logged to the console when the component is created?

export class MyComponent implements OnInit {
  constructor() { console.log('Constructor called'); }
  ngOnInit() { console.log('ngOnInit called'); }
}

medium

A. Constructor called\nngOnInit called

B. ngOnInit called\nConstructor called

C. Only Constructor called

D. Only ngOnInit called

Solution

1. Step 1: Understand Angular component creation order

   The constructor runs first when the component is created, then ngOnInit runs after Angular sets input properties.

2. Step 2: Trace the console logs

   First, 'Constructor called' logs, then 'ngOnInit called' logs.

3. Final Answer:

   Constructor called\nngOnInit called -> Option A

4. Quick Check:

   Constructor runs before ngOnInit [OK]

Hint: Constructor runs before ngOnInit [OK]

Common Mistakes:

• Thinking ngOnInit runs before constructor
• Expecting only one log message
• Confusing lifecycle order

4. What is wrong with this Angular component code snippet?

export class SampleComponent implements OnInit {
  ngOnInit() {
    this.loadData();
  }
  loadData() {
    console.log('Data loaded');
  }
  ngOnDestroy() {
    this.loadData();
  }
}

medium

A. ngOnInit should not be implemented without a constructor.

B. ngOnDestroy must return a value.

C. Calling loadData() inside ngOnDestroy is incorrect because it runs when component is destroyed.

D. loadData() cannot be called inside lifecycle hooks.

Solution

1. Step 1: Understand purpose of ngOnDestroy

   ngOnDestroy runs when the component is about to be removed. It is used to clean up resources, not to load data.

2. Step 2: Identify misuse of loadData()

   Calling loadData() during destruction is illogical because loading data is for initialization, not cleanup.

3. Final Answer:

   Calling loadData() inside ngOnDestroy is incorrect because it runs when component is destroyed. -> Option C

4. Quick Check:

   ngOnDestroy is for cleanup, not loading data [OK]

Hint: Use ngOnDestroy only for cleanup tasks [OK]

Common Mistakes:

• Thinking ngOnDestroy needs a return value
• Believing lifecycle hooks can't call methods
• Assuming constructor is required with ngOnInit

5. You want to fetch user data only once when a component loads and clean up a subscription when the component is destroyed. Which lifecycle hooks should you use together?

hard

A. ngOnChanges to fetch data, ngDoCheck to clean up subscription

B. ngOnInit to fetch data, ngOnDestroy to clean up subscription

C. constructor to fetch data, ngAfterViewInit to clean up subscription

D. ngAfterContentInit to fetch data, ngAfterContentChecked to clean up subscription

Solution

1. Step 1: Identify hook for initial data fetch

   Use ngOnInit to run code once after component creation, perfect for fetching data.

2. Step 2: Identify hook for cleanup

   Use ngOnDestroy to clean up resources like subscriptions before component is removed.

3. Final Answer:

   ngOnInit to fetch data, ngOnDestroy to clean up subscription -> Option B

4. Quick Check:

   Init = fetch, Destroy = cleanup [OK]

Hint: Fetch in ngOnInit, clean in ngOnDestroy [OK]

Common Mistakes:

• Using constructor for async data fetch
• Confusing ngAfterViewInit with cleanup
• Using ngOnChanges for one-time fetch