Storage vs memory vs calldata in Blockchain / Solidity - Performance Comparison

Time Complexity: Storage vs memory vs calldata

O(n)

Understanding Time Complexity

When working with blockchain smart contracts, how data is stored and accessed affects how long operations take.

We want to understand how the choice between storage, memory, and calldata changes the time cost as data size grows.

Scenario Under Consideration

Analyze the time complexity of the following Solidity function that copies an array from calldata to memory and then to storage.

function copyArray(uint[] calldata input) external {
    uint[] memory temp = new uint[](input.length);
    for (uint i = 0; i < input.length; i++) {
        temp[i] = input[i];
    }
    storedArray = temp;
}
    

This function copies an array received as calldata into memory, then saves it to storage.

Identify Repeating Operations

Look for loops or repeated steps that grow with input size.

• Primary operation: The for-loop copying each element from calldata to memory.
• How many times: Exactly once for each element in the input array.

How Execution Grows With Input

As the input array gets bigger, the loop runs more times, copying each element.

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

Pattern observation: The number of operations grows directly with the size of the input.

Final Time Complexity

Time Complexity: O(n)

This means the time to copy data grows linearly as the input size increases.

Common Mistake

[X] Wrong: "Accessing storage, memory, or calldata all take the same time regardless of data size."

[OK] Correct: Storage access is slower and costs more gas because it writes to blockchain state, while memory and calldata are faster but still depend on data size when copying.

Interview Connect

Understanding how data location affects time cost helps you write efficient smart contracts and shows you know how blockchain resources work.

Self-Check

What if we changed the function to copy data directly from calldata to storage without using memory? How would the time complexity change?

Practice

1. Which of the following correctly describes storage in Solidity?

easy

A. It stores data permanently on the blockchain.

B. It holds temporary data only during function execution.

C. It is used for read-only input data in external functions.

D. It is a type of event logging mechanism.

Solution

1. Step 1: Understand storage role

   storage variables are saved permanently on the blockchain and persist between function calls.

2. Step 2: Compare with memory and calldata

   memory is temporary during function execution, and calldata is read-only input data for external functions.

3. Final Answer:

   It stores data permanently on the blockchain. -> Option A

4. Quick Check:

   Storage = permanent data [OK]

Hint: Storage is permanent, memory is temporary, calldata is input [OK]

Common Mistakes:

• Confusing storage with memory as temporary
• Thinking calldata can be modified
• Assuming storage is read-only

2. Which keyword is used to declare a function parameter that is read-only and passed from an external caller?

easy

A. calldata

B. storage

C. memory

D. event

Solution

1. Step 1: Identify parameter data location for external input

   Function parameters from external callers that should not be modified use calldata.

2. Step 2: Recall other data locations

   memory is for temporary data inside functions, storage is persistent, and event is unrelated to data location.

3. Final Answer:

   calldata -> Option A

4. Quick Check:

   External input = calldata [OK]

Hint: External read-only params use calldata [OK]

Common Mistakes:

• Using memory for external parameters
• Confusing event with data location
• Using storage for function parameters

3. What will be the output of this Solidity function when called externally with _data = [1, 2, 3]?

function process(uint[] calldata _data) external pure returns (uint) {
    uint sum = 0;
    for (uint i = 0; i < _data.length; i++) {
        sum += _data[i];
    }
    return sum;
}

medium

A. Runtime error

B. 6

C. Compilation error

D. 0

Solution

1. Step 1: Understand calldata usage

   The function receives an array _data as calldata, which is read-only but accessible for reading elements.

2. Step 2: Calculate sum of array elements

   Sum of [1, 2, 3] is 1 + 2 + 3 = 6, which is returned.

3. Final Answer:

   6 -> Option B

4. Quick Check:

   Sum of input array = 6 [OK]

Hint: Sum array elements from calldata works like memory [OK]

Common Mistakes:

• Thinking calldata cannot be read
• Expecting compilation error due to calldata
• Confusing sum calculation logic

4. Identify the error in this Solidity function:

function updateData(uint[] calldata _input) external {
    _input[0] = 10;
}

medium

A. Calldata arrays cannot be passed as parameters.

B. Function must be marked pure.

C. Missing return statement.

D. Cannot assign to calldata array elements.

Solution

1. Step 1: Check mutability of calldata

   calldata is read-only, so assigning to _input[0] causes an error.

2. Step 2: Validate other options

   The function can be non-pure, no return needed, and calldata arrays are allowed as parameters.

3. Final Answer:

   Cannot assign to calldata array elements. -> Option D

4. Quick Check:

   Calldata is read-only [OK]

Hint: Calldata arrays are read-only, no assignment allowed [OK]

Common Mistakes:

• Trying to modify calldata elements
• Thinking pure is required here
• Assuming return is mandatory

5. You want to write a Solidity function that accepts a large array from an external caller, processes it temporarily, and then stores the result permanently. Which combination of data locations should you use for the parameter and the storage variable?

hard

A. Parameter as memory, storage variable as calldata

B. Parameter as storage, storage variable as memory

C. Parameter as calldata, storage variable as storage

D. Parameter as calldata, storage variable as memory

Solution

1. Step 1: Choose parameter data location for large external input

   calldata is efficient and read-only for large external arrays, avoiding unnecessary copying.

2. Step 2: Choose storage variable for permanent data

   To keep data permanently on blockchain, use storage for the variable that stores the processed result.

3. Final Answer:

   Parameter as calldata, storage variable as storage -> Option C

4. Quick Check:

   External input = calldata, permanent store = storage [OK]

Hint: Use calldata for input, storage for permanent save [OK]

Common Mistakes:

• Using memory for large external input (inefficient)
• Trying to store permanent data in memory or calldata
• Confusing storage and memory roles