Signal creation and reading in Angular - Performance & Optimization

Performance: Signal creation and reading

MEDIUM IMPACT

This affects how quickly Angular updates the UI when data changes and how efficiently it tracks dependencies.

Updating UI reactively based on data changes

Angular

const count = signal(0);

function increment() {
  count.set(count() + 1);
}

// Read signal once outside the loop
const currentCount = count();
for(let i = 0; i < 1000; i++) {
  console.log(currentCount);
}

Reading the signal once avoids repeated dependency tracking and reduces CPU work.

📈 Performance GainReduces redundant recalculations and microtasks, improving input responsiveness (INP).

Updating UI reactively based on data changes

Angular

const count = signal(0);

function increment() {
  count.set(count() + 1);
}

// Reading signal inside a heavy loop or multiple times unnecessarily
for(let i = 0; i < 1000; i++) {
  console.log(count());
}

Reading the signal multiple times inside a loop causes repeated dependency tracking and can trigger many unnecessary updates.

📉 Performance CostTriggers multiple recalculations and can cause many microtasks, increasing CPU usage and slowing responsiveness.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Reading signal multiple times in loop	Low DOM ops	Triggers multiple change detection cycles	Low paint cost	[X] Bad
Reading signal once and caching value	Low DOM ops	Single change detection cycle	Low paint cost	[OK] Good

Rendering Pipeline

Signal creation sets up reactive data sources. Reading signals registers dependencies. When signals update, Angular schedules change detection to update the DOM.

→Dependency Tracking

→Change Detection

→DOM Update

⚠️ BottleneckExcessive signal reads cause repeated dependency tracking and frequent change detection cycles.

Core Web Vital Affected

INP

This affects how quickly Angular updates the UI when data changes and how efficiently it tracks dependencies.

Optimization Tips

1Read signals minimally to avoid repeated dependency tracking.

2Cache signal values outside loops or repeated code blocks.

3Avoid creating signals inside frequently executed code paths.

Performance Quiz - 3 Questions

What is a performance risk when reading a signal multiple times inside a loop?

A It causes repeated dependency tracking and slows input responsiveness.

B It increases the bundle size significantly.

C It blocks the initial page load.

D It causes layout shifts on the page.

DevTools: Performance

How to check: Record a performance profile while interacting with the app. Look for frequent change detection cycles and microtasks related to signal updates.

What to look for: High number of change detection events or repeated microtasks indicates inefficient signal reading.

Practice

1. What does the signal function do in Angular?

easy

A. Registers a service for dependency injection

B. Defines a new Angular component

C. Creates a reactive value that can be read and updated

D. Starts an HTTP request

Solution

1. Step 1: Understand the purpose of signal

   The signal function is used to create reactive values that Angular tracks for changes.

2. Step 2: Identify what signal does

   It creates a value container that can be read by calling it and updated to trigger UI changes.

3. Final Answer:

   Creates a reactive value that can be read and updated -> Option C

4. Quick Check:

   Signal creation = reactive value container [OK]

Hint: Remember: signal() creates reactive values you can read and update [OK]

Common Mistakes:

• Confusing signal with component or service creation
• Thinking signal starts HTTP requests
• Assuming signal is for styling or templates

2. Which of the following is the correct way to create a signal with initial value 10?

easy

A. const count = signal(10);

B. const count = Signal(10);

C. const count = signal = 10;

D. const count = signal.create(10);

Solution

1. Step 1: Check the correct syntax for signal creation

   The correct syntax uses lowercase signal as a function with the initial value in parentheses.

2. Step 2: Compare options

   const count = signal(10); matches the correct syntax: const count = signal(10);. Others use wrong casing or invalid syntax.

3. Final Answer:

   const count = signal(10); -> Option A

4. Quick Check:

   signal() function call with initial value [OK]

Hint: Use lowercase signal() with parentheses for initial value [OK]

Common Mistakes:

• Using uppercase Signal instead of signal
• Assigning signal = 10 instead of calling signal(10)
• Trying to call a create method on signal

3. Given this code:

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

What will be printed in the console?

medium

A. 5 then 10

B. 5 then 5

C. 10 then 10

D. Error because set() is not a function

Solution

1. Step 1: Read the initial signal value

   The signal count is created with initial value 5, so count() returns 5.

2. Step 2: Update the signal and read again

   Calling count.set(10) updates the value to 10, so the next count() returns 10.

3. Final Answer:

   5 then 10 -> Option A

4. Quick Check:

   Signal read before and after set() = 5, 10 [OK]

Hint: Remember: signal() reads, set() updates value [OK]

Common Mistakes:

• Thinking count() returns the same value after set()
• Assuming set() is not a valid method
• Confusing signal reading with direct variable access

4. Identify the error in this code snippet:

const name = signal('Alice');
console.log(name);
name('Bob');

medium

A. Cannot call signal variable as a function

B. Missing parentheses when reading signal value

C. Cannot assign new value by calling signal as function

D. Signal must be updated using name.set('Bob')

Solution

1. Step 1: Check how signal values are read and updated

   Signals are read by calling them as functions: name(). To update, use name.set(newValue).

2. Step 2: Identify the error in updating

   The code tries to update the signal by calling name('Bob'), which is invalid. The correct way is name.set('Bob').

3. Final Answer:

   Signal must be updated using name.set('Bob') -> Option D

4. Quick Check:

   Update signals with set() method [OK]

Hint: Use set() to update signals, not calling them as functions [OK]

Common Mistakes:

• Trying to update signal by calling it as a function
• Forgetting parentheses when reading signal value
• Confusing signal with normal variables

5. You want to create a signal that holds a list of numbers and update it by adding a new number. Which code correctly updates the signal to add 4 to the list?

const numbers = signal([1, 2, 3]);
// Add 4 to numbers here

hard

A. numbers([...numbers(), 4]);

B. numbers.set([...numbers(), 4]);

C. numbers.value.push(4);

D. numbers = [...numbers(), 4];

Solution

1. Step 1: Understand how to read and update signals

   Read the current value by calling numbers(). To update, use numbers.set(newValue).

2. Step 2: Add 4 to the existing array immutably

   Create a new array with existing values plus 4: [...numbers(), 4]. Then update signal with numbers.set([...numbers(), 4]).

3. Final Answer:

   numbers.set([...numbers(), 4]); -> Option B

4. Quick Check:

   Update signal immutably with set([...signal(), newItem]) [OK]

Hint: Use set() with new array copy to update list signals [OK]

Common Mistakes:

• Trying to call signal as a function to update
• Mutating array directly without set()
• Assigning new array to signal variable directly