Storage vs memory usage in Blockchain / Solidity - Performance Comparison

Time Complexity: Storage vs memory usage

O(n)

Understanding Time Complexity

When working with blockchain, it's important to know how using storage and memory affects how long your code takes to run.

We want to see how the time needed changes when we use storage or memory for data.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

contract Example {
    uint[] storageData;

    function addToStorage(uint value) public {
        storageData.push(value);
    }

    function sumStorage() public view returns (uint) {
        uint sum = 0;
        for (uint i = 0; i < storageData.length; i++) {
            sum += storageData[i];
        }
        return sum;
    }

    function sumMemory(uint[] memory data) public pure returns (uint) {
        uint sum = 0;
        for (uint i = 0; i < data.length; i++) {
            sum += data[i];
        }
        return sum;
    }
}

This contract stores numbers in blockchain storage and sums them either from storage or from memory.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Looping through the array elements to sum values.
• How many times: Once for each element in the array (n times).

How Execution Grows With Input

As the number of elements grows, the time to sum them grows too.

Input Size (n)	Approx. Operations
10	10 additions
100	100 additions
1000	1000 additions

Pattern observation: The time grows directly with the number of items; doubling items doubles the work.

Final Time Complexity

Time Complexity: O(n)

This means the time to sum the array grows in a straight line with the number of elements.

Common Mistake

[X] Wrong: "Accessing storage and memory costs the same time per element."

[OK] Correct: Reading from storage is slower and costs more gas than reading from memory, so loops over storage take more time and resources.

Interview Connect

Understanding how storage and memory affect time helps you write efficient blockchain code and shows you know how to manage costs and speed.

Self-Check

"What if we copied the storage array to memory before summing? How would the time complexity change?"

Practice

1. Which of the following best describes storage in blockchain smart contracts?

easy

A. Permanent data saved on the blockchain that persists between function calls.

B. Temporary data used only during a function execution and discarded afterward.

C. Data stored off-chain for faster access.

D. Encrypted data that cannot be accessed by the contract.

Solution

1. Step 1: Understand storage purpose

   Storage holds data permanently on the blockchain, so it remains after function execution.

2. Step 2: Compare with memory

   Memory is temporary and only lasts during function execution, unlike storage.

3. Final Answer:

   Permanent data saved on the blockchain that persists between function calls. -> Option A

4. Quick Check:

   Storage = permanent data [OK]

Hint: Storage keeps data after functions finish, memory does not [OK]

Common Mistakes:

• Confusing memory with storage permanence
• Thinking storage is temporary
• Assuming storage is off-chain
• Believing storage is encrypted by default

2. Which of the following is the correct way to declare a variable in Solidity that uses memory?

easy

A. uint memory[] numbers;

B. uint[] storage numbers;

C. memory uint[] numbers;

D. uint[] memory numbers;

Solution

1. Step 1: Recall Solidity syntax for memory arrays

   In Solidity, the correct syntax is type[] memory variableName; for memory arrays.

2. Step 2: Check each option

   uint[] memory numbers; matches the correct syntax: uint[] memory numbers;. Others have wrong order or keywords.

3. Final Answer:

   uint[] memory numbers; -> Option D

4. Quick Check:

   Memory arrays use 'type[] memory name' syntax [OK]

Hint: Memory keyword comes after type and brackets in Solidity [OK]

Common Mistakes:

• Placing 'memory' before type
• Using 'storage' instead of 'memory'
• Incorrect array syntax
• Missing brackets for array type

3. What will be the output of the following Solidity function?

pragma solidity ^0.8.0;
contract Test {
    uint[] storageArray;
    function addAndReturn() public returns (uint) {
        uint[] memory tempArray = new uint[](1);
        tempArray[0] = 5;
        storageArray.push(10);
        return tempArray[0];
    }
}

medium

A. 0

B. 10

C. 5

D. Compilation error

Solution

1. Step 1: Analyze tempArray usage

   The function creates a memory array with one element set to 5, then returns that element.

2. Step 2: Understand storageArray effect

   storageArray.push(10) adds 10 to storage but does not affect the returned value.

3. Final Answer:

   5 -> Option C

4. Quick Check:

   Return value from memory array = 5 [OK]

Hint: Return value from memory array, storage change doesn't affect output [OK]

Common Mistakes:

• Confusing storage push with return value
• Expecting storageArray value as output
• Thinking memory array persists after function
• Assuming compilation error due to storage usage

4. Identify the error in this Solidity function that tries to copy a storage array to memory:

pragma solidity ^0.8.0;
contract Example {
    uint[] storageArray;
    function copyArray() public view returns (uint[] memory) {
        uint[] memory tempArray = storageArray;
        return tempArray;
    }
}

medium

A. Cannot assign storage array directly to memory array.

B. Function must be non-view to modify storage.

C. Missing visibility specifier for storageArray.

D. Memory arrays cannot be returned from functions.

Solution

1. Step 1: Understand storage to memory assignment

   In Solidity, you cannot directly assign a storage array to a memory array variable.

2. Step 2: Identify correct copying method

   You must copy elements manually or use a loop to transfer data from storage to memory.

3. Final Answer:

   Cannot assign storage array directly to memory array. -> Option A

4. Quick Check:

   Direct storage to memory assignment is invalid [OK]

Hint: Storage arrays need manual copying to memory arrays [OK]

Common Mistakes:

• Trying direct assignment from storage to memory
• Ignoring need for loops to copy arrays
• Assuming view functions can modify storage
• Believing memory arrays can't be returned

5. You want to write a Solidity function that temporarily modifies an array for calculations without changing the stored data. Which is the best approach?

hard

A. Declare the array as memory in the contract state.

B. Copy the storage array to a memory array, modify the memory array, then discard it.

C. Use a storage pointer to the array and modify it temporarily.

D. Modify the storage array directly and revert changes after calculations.

Solution

1. Step 1: Understand temporary modification needs

   To avoid changing stored data, use a memory copy for temporary changes.

2. Step 2: Evaluate options

   Copy the storage array to a memory array, modify the memory array, then discard it. copies storage to memory, modifies memory, and discards changes, preserving storage.

3. Step 3: Reject incorrect options

   A declares memory in state (invalid syntax); B risks permanent changes if revert fails; C modifies storage directly.

4. Final Answer:

   Copy the storage array to a memory array, modify the memory array, then discard it. -> Option B

5. Quick Check:

   Use memory copy for temporary changes [OK]

Hint: Use memory copy to avoid changing stored data permanently [OK]

Common Mistakes:

• Modifying storage directly for temporary needs
• Trying to declare storage variables as memory in contract
• Assuming revert undoes all changes safely
• Using storage pointers for temporary changes