Computed properties for derived state in Vue - Performance & Optimization

Performance: Computed properties for derived state

MEDIUM IMPACT

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

Calculating a value derived from reactive data for display

Vue

const doubled = computed(() => count.value * 2);

Computed caches the result and only recalculates when dependencies change, reducing updates.

📈 Performance Gainsingle reactive update and minimal re-renders

Calculating a value derived from reactive data for display

Vue

const doubled = ref(0);
watch(() => count.value, (newVal) => {
  doubled.value = newVal * 2;
});

Manually updating derived state causes extra watchers and can trigger multiple re-renders.

📉 Performance Costtriggers multiple reactive updates and re-renders on each change

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Manual watcher updating derived state	Multiple reactive triggers	Multiple reflows per update	Higher paint cost due to redundant updates	[X] Bad
Computed property for derived state	Single reactive trigger	Single reflow per update	Lower paint cost due to caching	[OK] Good

Rendering Pipeline

Computed properties run during the reactive update phase before rendering. They cache results to avoid redundant recalculations, reducing layout and paint work.

→Reactive Update

→Style Calculation

→Layout

→Paint

⚠️ BottleneckExcessive recalculations in reactive updates cause unnecessary layout and paint.

Core Web Vital Affected

INP

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

Optimization Tips

1Use computed properties to cache derived state and avoid redundant recalculations.

2Avoid manual watchers for derived state to reduce reactive update overhead.

3Efficient computed properties improve UI responsiveness and reduce unnecessary re-renders.

Performance Quiz - 3 Questions

Why are computed properties better than manual watchers for derived state in Vue?

A They cache results and only recalculate when dependencies change

B They always recalculate on every render

C They block the main thread longer

D They increase bundle size significantly

DevTools: Performance

How to check: Record a performance profile while interacting with the component. Look for repeated recalculations or reactive updates in the flame chart.

What to look for: Fewer recalculations and shorter update times indicate efficient computed property usage.

Practice

1. What is the main purpose of a computed property in Vue?

easy

A. To directly modify the DOM elements

B. To store static data that never changes

C. To create a value that updates automatically when its dependencies change

D. To replace methods for event handling

Solution

1. Step 1: Understand computed property role

   Computed properties automatically update when their reactive dependencies change, unlike static data.

2. Step 2: Compare with other options

   Static data does not update automatically, DOM manipulation is done differently, and event handling uses methods or event listeners.

3. Final Answer:

   To create a value that updates automatically when its dependencies change -> Option C

4. Quick Check:

   Computed properties = auto-updating values [OK]

Hint: Computed properties auto-update when data changes [OK]

Common Mistakes:

• Thinking computed properties store static data
• Confusing computed with methods for events
• Assuming computed directly changes the DOM

2. Which of the following is the correct syntax to define a computed property named fullName using Vue's Composition API?

easy

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

B. const fullName = computed { return firstName + ' ' + lastName }

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

D. const fullName = computed(() => firstName.concat(lastName))

Solution

1. Step 1: Check correct computed syntax

   Vue's computed expects a function returning a value, so arrow function with parentheses and return expression is correct.

2. Step 2: Analyze each option

   const fullName = computed(() => fullName + ' ' + lastName) uses arrow function returning concatenated string correctly. const fullName = computed { return firstName + ' ' + lastName } has wrong syntax (missing parentheses). const fullName = computed(() => { firstName + ' ' + lastName }) lacks return statement in block. const fullName = computed(() => firstName.concat(lastName)) uses concat without space.

3. Final Answer:

   const fullName = computed(() => firstName + ' ' + lastName) -> Option A

4. Quick Check:

   Correct computed syntax = const fullName = computed(() => firstName + ' ' + lastName) [OK]

Hint: Use arrow function with return expression inside computed [OK]

Common Mistakes:

• Omitting parentheses in computed call
• Forgetting return in block arrow function
• Using string concat without space

3. Given the following Vue setup code, what will be the output of fullName.value?

import { ref, computed } from 'vue'
const firstName = ref('Jane')
const lastName = ref('Doe')
const fullName = computed(() => firstName.value + ' ' + lastName.value)

firstName.value = 'John'

medium

A. undefined

B. "Jane Doe"

C. "Jane John"

D. "John Doe"

Solution

1. Step 1: Understand reactive refs and computed

   firstName and lastName are reactive refs. Changing firstName.value updates computed fullName automatically.

2. Step 2: Evaluate fullName after update

   After setting firstName.value = 'John', fullName.value becomes 'John Doe' because computed uses current ref values.

3. Final Answer:

   "John Doe" -> Option D

4. Quick Check:

   Computed updates with ref changes = "John Doe" [OK]

Hint: Computed reflects latest ref values automatically [OK]

Common Mistakes:

• Assuming computed keeps old value
• Ignoring .value when accessing refs
• Confusing variable names in output

4. Identify the error in this Vue computed property code:

import { ref, computed } from 'vue'
const count = ref(0)
const doubleCount = computed(() => {
  count + 2
})

medium

A. Missing return statement inside computed function

B. count should not be a ref

C. computed should be imported from 'vuex'

D. doubleCount should be a method, not computed

Solution

1. Step 1: Check computed function body

   The arrow function uses braces but does not return a value explicitly, so it returns undefined.

2. Step 2: Correct usage

   Either remove braces or add a return statement to return count.value + 2.

3. Final Answer:

   Missing return statement inside computed function -> Option A

4. Quick Check:

   Computed with braces needs return [OK]

Hint: Add return when using braces in arrow function [OK]

Common Mistakes:

• Forgetting return in block arrow functions
• Importing computed from wrong package
• Misusing ref as normal variable

5. You have a list of products with prices and quantities as refs. How would you create a computed property totalPrice that sums the product of price and quantity for all products? Choose the correct computed property code snippet:

hard

A. const totalPrice = computed(() => products.reduce((sum, p) => sum + p.price * p.quantity, 0))

B. const totalPrice = computed(() => products.value.reduce((sum, p) => sum + p.price.value * p.quantity.value, 0))

C. const totalPrice = computed(() => { products.value.forEach(p => sum += p.price.value * p.quantity.value); return sum })

D. const totalPrice = computed(() => products.value.map(p => p.price.value * p.quantity.value))

Solution

1. Step 1: Understand data structure and refs

   Each product has price and quantity as refs, so access with .value. products is a ref array, so use products.value.

2. Step 2: Choose correct aggregation method

   Use reduce to sum all price * quantity values. const totalPrice = computed(() => products.value.reduce((sum, p) => sum + p.price.value * p.quantity.value, 0)) correctly uses reduce with .value access and initial sum 0.

3. Step 3: Analyze incorrect options

   const totalPrice = computed(() => products.reduce((sum, p) => sum + p.price * p.quantity, 0)) misses .value on refs. const totalPrice = computed(() => { products.value.forEach(p => sum += p.price.value * p.quantity.value); return sum }) uses forEach but sum is undefined. const totalPrice = computed(() => products.value.map(p => p.price.value * p.quantity.value)) returns array, not sum.

4. Final Answer:

   const totalPrice = computed(() => products.value.reduce((sum, p) => sum + p.price.value * p.quantity.value, 0)) -> Option B

5. Quick Check:

   Use reduce with .value refs to sum totals [OK]

Hint: Use reduce with .value to sum reactive refs [OK]

Common Mistakes:

• Forgetting .value on refs inside products
• Using map instead of reduce for sum
• Not initializing sum in reduce