Signal vs observable comparison in Angular - Performance Comparison

Performance: Signal vs observable comparison

MEDIUM IMPACT

This concept affects how Angular apps handle data updates and UI rendering speed.

Updating UI reactively when data changes

Angular

const value = signal(initialValue); // Signal usage
value.set(newValue); // Updates UI reactively with minimal overhead

Signals trigger precise UI updates without full change detection cycles.

📈 Performance GainSingle targeted update, reducing CPU and memory usage.

Updating UI reactively when data changes

Angular

this.data$.subscribe(value => { this.value = value; }); // Observable subscription in component

Observables can cause multiple change detection cycles and extra memory usage if not managed well.

📉 Performance CostTriggers multiple change detection runs and can cause memory leaks if subscriptions are not cleaned up.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Observable subscription with frequent updates	Multiple updates to DOM nodes	Multiple reflows per update	Higher paint cost due to broad changes	[X] Bad
Signal with direct reactive updates	Minimal DOM node updates	Single reflow per update	Lower paint cost with targeted changes	[OK] Good

Rendering Pipeline

Signals update only the parts of the UI that depend on them, minimizing style recalculations and layout changes. Observables trigger Angular's change detection which can re-check many components.

→Change Detection

→Style Calculation

→Layout

→Paint

⚠️ BottleneckChange Detection stage is most expensive with observables due to broad checks.

Core Web Vital Affected

INP

This concept affects how Angular apps handle data updates and UI rendering speed.

Optimization Tips

1Use signals to minimize Angular's change detection scope.

2Always unsubscribe from observables to avoid memory leaks.

3Signals provide more precise and efficient UI updates than observables.

Performance Quiz - 3 Questions

Which pattern reduces Angular's change detection overhead the most?

A Using observables with manual subscription

B Using signals for reactive updates

C Using setTimeout to delay updates

D Using event emitters for all data changes

DevTools: Performance

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

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

Practice

1. Which statement best describes an Angular signal compared to an observable?

easy

A. A signal requires manual subscription to receive updates.

B. A signal handles multiple asynchronous events over time.

C. A signal holds a single reactive value and updates UI automatically.

D. A signal is used only for HTTP requests.

Solution

1. Step 1: Understand what a signal represents

   Signals hold a single reactive value that updates the UI automatically when changed.

2. Step 2: Compare with observable behavior

   Observables handle streams of data over time and require subscriptions, unlike signals.

3. Final Answer:

   A signal holds a single reactive value and updates UI automatically. -> Option C

4. Quick Check:

   Signal = single reactive value [OK]

Hint: Signals hold one value; observables handle streams [OK]

Common Mistakes:

• Thinking signals handle multiple async events like observables
• Believing signals require subscriptions
• Confusing signals with HTTP request handlers

2. Which of the following is the correct way to create a signal in Angular?

easy

A. const count = new Observable(0);

B. const count = signal(0);

C. const count = subscribe(0);

D. const count = createObservable(0);

Solution

1. Step 1: Recall Angular signal creation syntax

   Signals are created using the signal() function with an initial value.

2. Step 2: Identify incorrect options

   Observable creation uses new Observable(), subscribe is a method, and createObservable() is not valid.

3. Final Answer:

   const count = signal(0); -> Option B

4. Quick Check:

   signal() creates signals [OK]

Hint: Use signal() function to create signals [OK]

Common Mistakes:

• Using new Observable() to create a signal
• Confusing subscribe() with signal creation
• Using non-existent createObservable() function

3. Given the code below, what will be logged to the console?

const count = signal(1);
count.set(5);
console.log(count());

medium

A. 1

B. An error because signals cannot be set

C. undefined

D. 5

Solution

1. Step 1: Understand signal value update

   The signal is created with initial value 1, then updated to 5 using set().

2. Step 2: Check the value returned by calling the signal

   Calling count() returns the current value, which is 5 after set().

3. Final Answer:

   5 -> Option D

4. Quick Check:

   Signal value after set() = 5 [OK]

Hint: Calling signal() returns current value [OK]

Common Mistakes:

• Assuming initial value remains after set()
• Thinking signals cannot be updated
• Confusing signal() call with observable subscription

4. What is wrong with this Angular code using an observable?

const obs = new Observable(subscriber => {
  subscriber.next(1);
});
obs.next(2);

medium

A. Observables do not have a next() method on the instance.

B. Observable must be created with signal() instead.

C. Subscriber function cannot call next().

D. Observable must be subscribed before calling next().

Solution

1. Step 1: Understand Observable instance methods

   Observable instances do not have a next() method; next() is called on the subscriber inside the constructor.

2. Step 2: Identify misuse of next() outside subscriber

   Calling obs.next(2) is invalid and causes an error.

3. Final Answer:

   Observables do not have a next() method on the instance. -> Option A

4. Quick Check:

   next() is on subscriber, not observable instance [OK]

Hint: next() is called inside subscriber, not on observable [OK]

Common Mistakes:

• Trying to call next() on observable instance
• Confusing signal() with observable creation
• Believing subscription is needed before next()

5. You want to manage a simple counter state that updates the UI immediately when changed. Which approach is best and why?

Option A: Use a signal to hold the counter value.
Option B: Use an observable and subscribe to updates.
Option C: Use a Promise to fetch the counter value.
Option D: Use a BehaviorSubject without subscription.

hard

A. Signal is best because it holds a single reactive value and updates UI automatically.

B. Observable is best because it handles multiple async events efficiently.

C. Promise is best because it resolves once with the counter value.

D. BehaviorSubject without subscription updates UI automatically.

Solution

1. Step 1: Identify the requirement for simple immediate UI update

   A simple counter state that updates UI immediately fits the signal use case.

2. Step 2: Compare other options

   Observable requires subscription and is better for streams; Promise resolves once; BehaviorSubject needs subscription to update UI.

3. Final Answer:

   Signal is best because it holds a single reactive value and updates UI automatically. -> Option A

4. Quick Check:

   Simple state + auto UI update = signal [OK]

Hint: Use signals for simple reactive state, observables for streams [OK]

Common Mistakes:

• Choosing observable for simple state without subscription
• Using Promise for reactive UI updates
• Assuming BehaviorSubject updates UI without subscription