Computed signals for derived values in Angular - Performance & Optimization

Performance: Computed signals for derived values

MEDIUM IMPACT

This affects how efficiently Angular updates the UI when derived data changes, impacting interaction responsiveness and rendering speed.

Updating UI based on derived state from multiple signals

Angular

const count = signal(0);
const multiplier = signal(2);
const derivedValue = computed(() => count() * multiplier());

// UI automatically updates when derivedValue changes
effect(() => {
  updateUI(derivedValue());
});

Computed signal caches and recalculates only when dependencies change, batching updates efficiently.

📈 Performance GainSingle recalculation and UI update per change, reducing INP latency significantly.

Updating UI based on derived state from multiple signals

Angular

const count = signal(0);
const multiplier = signal(2);

// Manually using separate effects to update derived value
let derivedValue = 0;
effect(() => {
  derivedValue = count() * multiplier();
  updateUI(derivedValue);
});

Manually using separate effects causes multiple recalculations and UI updates, leading to redundant work and slower interaction.

📉 Performance CostTriggers multiple recalculations and DOM updates per change, increasing INP latency.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Manual separate effects for derived values	Multiple redundant DOM updates	Multiple reflows per dependency change	High paint cost due to repeated updates	[X] Bad
Computed signals for derived values	Single DOM update per change	Single reflow per change	Minimal paint cost with batched updates	[OK] Good

Rendering Pipeline

Computed signals optimize the update flow by recalculating derived values only when their dependencies change, minimizing layout and paint work.

→Style Calculation

→Layout

→Paint

⚠️ BottleneckLayout and Paint stages due to unnecessary recalculations and DOM updates

Core Web Vital Affected

INP

This affects how efficiently Angular updates the UI when derived data changes, impacting interaction responsiveness and rendering speed.

Optimization Tips

1Use computed signals to memoize derived values and avoid redundant recalculations.

2Avoid manual subscriptions that cause multiple updates for the same derived data.

3Batch UI updates by relying on computed signals to improve interaction responsiveness.

Performance Quiz - 3 Questions

What is the main performance benefit of using computed signals for derived values in Angular?

A They recalculate derived values only when dependencies change, reducing unnecessary work.

B They increase the number of DOM updates to keep UI fresh.

C They block rendering until all signals update.

D They add extra subscriptions for better debugging.

DevTools: Performance

How to check: Record a performance profile while interacting with the UI that updates derived values. Look for multiple recalculations or layout thrashing in the flame chart.

What to look for: Fewer recalculations and shorter layout/paint times indicate good use of computed signals.

Practice

1. What is the main purpose of a computed signal in Angular's signal system?

easy

A. To replace all signals with a single global state

B. To store static data that never changes

C. To automatically update a value based on other signals when they change

D. To manually trigger UI updates

Solution

1. Step 1: Understand what computed signals do

   Computed signals derive their value from other signals and update automatically when those signals change.

2. Step 2: Compare options with this behavior

   Only To automatically update a value based on other signals when they change describes automatic updates based on dependencies, which matches computed signals.

3. Final Answer:

   To automatically update a value based on other signals when they change -> Option C

4. Quick Check:

   Computed signals = auto-update derived values [OK]

Hint: Computed signals auto-update when dependencies change [OK]

Common Mistakes:

• Thinking computed signals store static data
• Confusing manual updates with automatic updates
• Assuming computed signals replace all signals

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

easy

A. const total = computed(() => price() + tax());

B. const total = signal(() => price + tax);

C. const total = computed(price + tax);

D. const total = signal(price() + tax());

Solution

1. Step 1: Recall computed signal syntax

   Computed signals use computed(() => ...) with a function returning the derived value.

2. Step 2: Check each option

   const total = computed(() => price() + tax()); correctly uses computed(() => price() + tax()). const total = signal(() => price + tax); wrongly uses signal and no function. const total = computed(price + tax); misses the function wrapper. const total = signal(price() + tax()); uses signal instead of computed.

3. Final Answer:

   const total = computed(() => price() + tax()); -> Option A

4. Quick Check:

   Computed syntax = computed(() => value) [OK]

Hint: Use computed(() => ...) with a function for derived values [OK]

Common Mistakes:

• Using signal() instead of computed() for derived values
• Passing expressions directly without a function
• Not calling dependent signals as functions

3. Given the code below, what will be logged after count.set(5) is called?

const count = signal(0);
const double = computed(() => count() * 2);

console.log(double());
count.set(5);
console.log(double());

medium

A. 0 then 10

B. 0 then 0

C. NaN then 10

D. Error at runtime

Solution

1. Step 1: Evaluate initial values

   Initially, count is 0, so double() returns 0 * 2 = 0.

2. Step 2: After count.set(5)

   Setting count to 5 updates double automatically. Calling double() now returns 5 * 2 = 10.

3. Final Answer:

   0 then 10 -> Option A

4. Quick Check:

   Initial double=0, after update=10 [OK]

Hint: Computed updates automatically after signal changes [OK]

Common Mistakes:

• Assuming computed does not update after set()
• Forgetting to call signals as functions
• Expecting errors due to missing subscriptions

4. Identify the error in the following code snippet using computed signals:

const price = signal(100);
const tax = signal(0.1);
const total = computed(() => price + tax * price);

console.log(total());

medium

A. Computed signals cannot use arithmetic operations

B. Signals must be called as functions inside computed

C. Signals cannot be used inside computed

D. Missing initial value for tax signal

Solution

1. Step 1: Check how signals are accessed

   Signals are functions and must be called with () to get their current value.

2. Step 2: Analyze the computed expression

   The expression uses price and tax directly without calling them, so it uses the signal objects, not their values.

3. Final Answer:

   Signals must be called as functions inside computed -> Option B

4. Quick Check:

   Access signals with () inside computed [OK]

Hint: Always call signals as functions inside computed [OK]

Common Mistakes:

• Using signal variables directly without ()
• Thinking computed disallows arithmetic
• Ignoring signal initial values

5. You want to create a computed signal that returns the full name by combining two signals: firstName and lastName. Which code correctly updates the full name when either signal changes and avoids unnecessary recomputations?

hard

A. const fullName = computed(() => firstName() + lastName());

B. const fullName = signal(`${firstName()} ${lastName()}`);

C. const fullName = computed(() => firstName + ' ' + lastName);

D. const fullName = computed(() => `${firstName()} ${lastName()}`);

Solution

1. Step 1: Understand the goal

   The computed signal should combine firstName and lastName signals and update automatically when either changes.

2. Step 2: Evaluate each option

   const fullName = computed(() => `${firstName()} ${lastName()}`); correctly calls both signals as functions and concatenates with a space. const fullName = signal(`${firstName()} ${lastName()}`); uses signal which won't update automatically. const fullName = computed(() => firstName + ' ' + lastName); uses signal variables directly without calling them. const fullName = computed(() => firstName() + lastName()); concatenates without space.

3. Final Answer:

   const fullName = computed(() => `${firstName()} ${lastName()}`); -> Option D

4. Quick Check:

   Call signals with () and combine with space [OK]

Hint: Use computed with template literals calling signals () [OK]

Common Mistakes:

• Using signal() instead of computed() for derived values
• Not calling signals as functions
• Forgetting space between names