Why saving and loading matters in NumPy - Performance Analysis

Time Complexity: Why saving and loading matters

O(n)

Understanding Time Complexity

When working with data, saving and loading files can take time. We want to understand how this time changes as the data size grows.

How does the time to save or load data increase when the data gets bigger?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

import numpy as np

# Create a large array
arr = np.random.rand(1000000)

# Save the array to a file
np.save('data.npy', arr)

# Load the array from the file
loaded_arr = np.load('data.npy')

This code creates a large array, saves it to a file, and then loads it back into memory.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Reading or writing each element of the array to disk.
• How many times: Once for each element in the array during save and once during load.

How Execution Grows With Input

Explain the growth pattern intuitively.

Input Size (n)	Approx. Operations
10	About 10 operations to save and 10 to load
100	About 100 operations to save and 100 to load
1000	About 1000 operations to save and 1000 to load

Pattern observation: The time grows roughly in direct proportion to the number of elements. Double the data, double the time.

Final Time Complexity

Time Complexity: O(n)

This means the time to save or load grows linearly with the size of the data.

Common Mistake

[X] Wrong: "Saving or loading data takes the same time no matter how big the data is."

[OK] Correct: The computer must process each piece of data, so bigger data means more work and more time.

Interview Connect

Understanding how saving and loading time grows helps you write efficient data workflows and shows you think about real-world data handling.

Self-Check

"What if we compressed the data before saving? How would the time complexity change?"