Computed vs method performance in Vue - Visual Side-by-Side Comparison

Concept Flow - Computed vs method performance

Component Renders

↓

Access Computed Property

↓

Check Cache

↓

Display Value

↓

Access Method

↓

Run Method Function

↓

Return Result

↓

Display Value

When the component renders, accessing a computed property first checks if the cached value exists to reuse it, while calling a method runs the function every time without caching.

Execution Sample

Vue

const count = ref(0);
const doubleComputed = computed(() => count.value * 2);
function doubleMethod() { return count.value * 2; }

// Template uses {{ doubleComputed }} and {{ doubleMethod() }}

Shows a reactive count with a computed property and a method both doubling the count, used in the template.

Execution Table

Step	Action	count.value	Computed Cache	Method Called	Output Computed	Output Method
1	Initial render, count=0	0	0	No	Calculates 0*2=0 and caches	N/A
2	Template accesses computed	0	0	No	Returns cached 0	N/A
3	Template calls method	0	0	Yes	N/A	Calculates 0*2=0
4	count.value increments to 1	1	invalidated	No	N/A	N/A
5	Template accesses computed	1	2	No	Calculates 1*2=2 and caches	N/A
6	Template calls method	1	2	Yes	N/A	Calculates 1*2=2
7	count.value increments to 2	2	invalidated	No	N/A	N/A
8	Template accesses computed	2	4	No	Calculates 2*2=4 and caches	N/A
9	Template calls method	2	4	Yes	N/A	Calculates 2*2=4
10	End of trace	2	4	Yes	4	4

💡 Execution stops after showing how computed caches and method runs on each render and reactive change.

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	Final
count.value	0	0	0	1	1	2	2
Computed Cache	empty	0	0	invalidated	2	invalidated	4
Method Called	No	No	Yes	No	Yes	No	Yes
Output Computed	N/A	0	0	2	2	4	4
Output Method	N/A	N/A	0	N/A	2	N/A	4

Key Moments - 3 Insights

Why does the computed property not recalculate every time the template accesses it?

Because computed properties cache their result until their reactive dependencies change, as shown in execution_table rows 2 and 5 where the cached value is reused.

Why does the method run every time it is called in the template?

Methods are regular functions and do not cache results, so they run fresh on every call, as seen in execution_table rows 3, 6, and 9.

What causes the computed cache to invalidate and recalculate?

When a reactive dependency like count.value changes, the computed cache invalidates and recalculates on next access, shown in execution_table rows 4 and 7.

Visual Quiz - 3 Questions

Look at the execution_table at step 5. What is the computed cache value after recalculation?

A 0

B 2

C empty

D 4

💡 Hint

Check the 'Computed Cache' column at step 5 in the execution_table.

At which step does the method first run after count.value changes to 1?

A Step 6

B Step 5

C Step 4

D Step 7

💡 Hint

Look for 'Method Called' marked 'Yes' after count.value changes to 1 in execution_table.

If count.value never changes, how would the computed cache behave?

A It never caches

B It recalculates every time

C It caches once and reuses forever

D It clears cache every render

💡 Hint

Refer to the caching behavior shown in execution_table steps 1 and 2.

Concept Snapshot

Computed properties cache their results and only recalculate when dependencies change.
Methods run fresh every time they are called.
Use computed for expensive or repeated calculations.
Use methods for simple or event-driven calculations.
Computed improves performance by avoiding unnecessary recalculations.

Full Transcript

This visual trace shows how Vue's computed properties cache their results and only recalculate when reactive dependencies like count.value change. Methods, in contrast, run their function every time they are called in the template without caching. The execution table tracks count.value changes, computed cache state, method calls, and outputs step-by-step. Key moments clarify why computed properties improve performance by caching and when caches invalidate. The quiz tests understanding of cache values and method calls referencing the execution table. This helps beginners see the difference in behavior and performance between computed properties and methods in Vue.

Practice

1. Which statement best explains why computed properties are generally faster than methods in Vue?

easy

A. Computed properties cache their results and only recalculate when dependencies change.

B. Methods run only once and then cache their results automatically.

C. Computed properties run every time the component renders without caching.

D. Methods cache results and update only when data changes.

Solution

1. Step 1: Understand computed property behavior

   Computed properties remember their last result and only recalculate if their dependent data changes.

2. Step 2: Contrast with methods

   Methods run fresh every time they are called, without caching results.

3. Final Answer:

   Computed properties cache their results and only recalculate when dependencies change. -> Option A

4. Quick Check:

   Computed cache = B [OK]

Hint: Remember: computed caches, methods do not [OK]

Common Mistakes:

• Thinking methods cache results automatically
• Believing computed properties run every render
• Confusing when caching happens

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

easy

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

B. methods: { fullName() { return firstName + ' ' + lastName } }

C. computed: { fullName() { return firstName + ' ' + lastName } }

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

Solution

1. Step 1: Identify Composition API syntax

   In Vue 3 Composition API, computed properties are created by calling the computed function with a getter function.

2. Step 2: Check each option

   const fullName = computed(() => firstName + ' ' + lastName); correctly uses computed(() => ...). Options B and C use Options API syntax, and D is just a plain function without caching.

3. Final Answer:

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

4. Quick Check:

   Composition API computed = A [OK]

Hint: Composition API computed uses computed(() => ...) [OK]

Common Mistakes:

• Mixing Options API and Composition API syntax
• Using methods syntax for computed
• Not wrapping in computed() function

3. Given the Vue component below, what will be logged to the console when the button is clicked twice?

setup() {
  const count = ref(0);
  const doubleCount = computed(() => {
    console.log('Computed called');
    return count.value * 2;
  });
  function increment() {
    count.value++;
    console.log('Method called:', doubleCount.value);
  }
  return { count, doubleCount, increment };
}

medium

A. Method called: 0\nMethod called: 0

B. Computed called\nMethod called: 2\nMethod called: 4

C. Computed called\nMethod called: 2\nComputed called\nMethod called: 4

D. Computed called\nComputed called\nMethod called: 2\nMethod called: 4

Solution

1. Step 1: Understand computed caching and logging

   The computed property logs 'Computed called' only when recalculated. It recalculates when count.value changes.

2. Step 2: Trace the two button clicks

   First click: count=1 triggers computed recalculation (logs 'Computed called'), then method logs 'Method called: 2'. Second click: count=2 triggers computed recalculation again (logs 'Computed called'), then method logs 'Method called: 4'.

3. Final Answer:

   Computed called Method called: 2 Computed called Method called: 4 -> Option C

4. Quick Check:

   Computed logs twice, method logs twice = A [OK]

Hint: Computed logs only on dependency change, methods run every call [OK]

Common Mistakes:

• Assuming computed logs every method call
• Ignoring reactive dependency triggers
• Confusing method and computed logs

4. You have a Vue component where a method is used to calculate a value that depends on reactive data. The UI is slow because the method runs on every render. How can you fix this performance issue?

medium

A. Convert the method to a computed property so it caches results until dependencies change.

B. Wrap the method call inside a watch to run less often.

C. Use a lifecycle hook to call the method only once.

D. Move the method logic to a separate utility file.

Solution

1. Step 1: Identify the cause of slowness

   Methods run fresh every render, causing repeated calculations and slowing UI.

2. Step 2: Apply computed property for caching

   Computed properties cache results and only recalculate when reactive dependencies change, improving performance.

3. Final Answer:

   Convert the method to a computed property so it caches results until dependencies change. -> Option A

4. Quick Check:

   Use computed for caching = C [OK]

Hint: Switch slow methods to computed for caching [OK]

Common Mistakes:

• Using watch incorrectly to reduce method calls
• Thinking lifecycle hooks solve reactive recalculations
• Moving logic without caching benefits

5. You have a Vue 3 component that displays a filtered list based on a search term. The filtering is done inside a method called filteredList() which runs on every render, causing lag with large data. How can you optimize this using computed properties? Consider that the list and search term are reactive refs.

hard

A. Use a method but memoize results manually with a cache object.

B. Replace the method with a computed property that returns the filtered list, so filtering runs only when list or search term changes.

C. Move filtering logic to a watcher that updates a reactive variable with filtered results.

D. Keep the method but debounce the search input to reduce calls.

Solution

1. Step 1: Identify reactive dependencies

   The filtered list depends on the reactive list and search term, so it should update only when these change.

2. Step 2: Use computed property for caching

   Computed properties cache results and recalculate only when dependencies change, making filtering efficient.

3. Step 3: Compare other options

   Debouncing reduces calls but does not cache results. Watchers add complexity. Manual memoization is error-prone.

4. Final Answer:

   Replace the method with a computed property that returns the filtered list, so filtering runs only when list or search term changes. -> Option B

5. Quick Check:

   Use computed for reactive filtering = D [OK]

Hint: Use computed to cache filtered results by dependencies [OK]

Common Mistakes:

• Relying on debouncing without caching
• Using watchers unnecessarily
• Trying manual memoization instead of computed