Memory-efficient operations in Data Analysis Python - Step-by-Step Execution

Concept Flow - Memory-efficient operations

Load large data

↓

Choose memory-efficient data types

↓

Apply operations without copying

↓

Use generators or iterators

↓

Process data step-by-step

↓

Output results with low memory use

This flow shows how to handle large data by choosing efficient types, avoiding copies, and processing stepwise to save memory.

Execution Sample

Data Analysis Python

import pandas as pd

# Load data with specific dtypes
df = pd.DataFrame({'A': range(5), 'B': range(5, 10)})
df['A'] = df['A'].astype('int8')
df['B'] = df['B'].astype('int8')

# Use generator to process
result = (x * 2 for x in df['A'])
print(list(result))

This code converts columns to smaller integer types and uses a generator to double values without extra memory.

Execution Table

Step	Action	Variable State	Memory Use	Output
1	Create DataFrame with default int64	df: columns A and B as int64	High	None
2	Convert column A to int8	df['A']: int8, df['B']: int64	Reduced	None
3	Convert column B to int8	df['A']: int8, df['B']: int8	Further reduced	None
4	Create generator to double df['A']	result: generator object	Very low	None
5	Convert generator to list and print	result exhausted	Low	[0, 2, 4, 6, 8]
6	End of process	Variables remain, no copies made	Low	Final output shown

💡 Process ends after printing doubled values from generator, memory kept low by type conversion and generator use.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5	Final
df['A']	int64 values 0-4	int8 values 0-4	int8 values 0-4	int8 values 0-4	int8 values 0-4	int8 values 0-4
df['B']	int64 values 5-9	int64 values 5-9	int8 values 5-9	int8 values 5-9	int8 values 5-9	int8 values 5-9
result	None	None	None	generator object	exhausted generator	exhausted generator

Key Moments - 3 Insights

Why do we convert columns to smaller data types like int8?

Converting to smaller types reduces memory use significantly without changing data meaning, as shown in execution_table steps 2 and 3.

How does using a generator save memory compared to a list?

Generators produce items one by one without storing all at once, so memory stays low as seen in step 4 versus creating a full list.

Does converting columns change the original data?

No, it changes the data type in place without copying, keeping memory use low as shown by variable_tracker for df columns.

Visual Quiz - 3 Questions

Look at the execution_table at step 3, what is the data type of column 'B'?

A int64

B float64

C int8

D object

💡 Hint

Check the 'Variable State' column at step 3 in execution_table.

At which step does the generator get created?

A Step 4

B Step 3

C Step 2

D Step 5

💡 Hint

Look for 'Create generator' action in execution_table.

If we did not convert columns to int8, how would memory use change at step 3?

A Memory use would be lower

B Memory use would be higher

C Memory use would be the same

D Memory use would be zero

💡 Hint

Refer to memory use changes in execution_table steps 1 to 3.

Concept Snapshot

Memory-efficient operations:
- Convert data columns to smaller types (e.g., int8) to save memory
- Use generators to process data stepwise without full copies
- Avoid unnecessary copies to keep memory low
- Process large data in chunks or streams
- Check memory use before and after conversions

Full Transcript

This lesson shows how to save memory when working with data in Python. We start with a DataFrame with default large integer types. Then, we convert columns to smaller types like int8 to reduce memory use. Next, we create a generator to process data one item at a time, which uses very little memory. Finally, we convert the generator to a list to see the output. Throughout, we track variable types and memory use, showing how these steps keep memory low. Key points include converting data types and using generators instead of lists to save memory.

Practice

1. Which of the following is a common method to reduce memory usage when working with large datasets in Python?

easy

A. Increase the size of integer columns to 64-bit

B. Use print statements to debug data

C. Convert text columns to 'category' data type

D. Load the entire dataset into memory at once

Solution

1. Step 1: Understand memory usage of data types

   Text columns with repeated values use more memory as strings than as categories.

2. Step 2: Apply category conversion

   Converting text columns to 'category' type stores unique values once, saving memory.

3. Final Answer:

   Convert text columns to 'category' data type -> Option C

4. Quick Check:

   Category type reduces memory for repeated text [OK]

Hint: Convert repeated text columns to 'category' type to save memory [OK]

Common Mistakes:

• Thinking increasing integer size saves memory
• Loading full dataset without chunking
• Using print for memory optimization

2. Which of the following is the correct syntax to read a large CSV file in chunks of 1000 rows using pandas?

easy

A. pd.read_csv('file.csv', chunksize=1000)

B. pd.read_csv('file.csv', chunk=1000)

C. pd.read_csv('file.csv', size=1000)

D. pd.read_csv('file.csv', batch=1000)

Solution

1. Step 1: Recall pandas chunk reading parameter

   The correct parameter to read in chunks is 'chunksize'.

2. Step 2: Match syntax

   Only pd.read_csv('file.csv', chunksize=1000) uses 'chunksize=1000', which is correct syntax.

3. Final Answer:

   pd.read_csv('file.csv', chunksize=1000) -> Option A

4. Quick Check:

   chunksize=1000 reads file in 1000-row chunks [OK]

Hint: Use 'chunksize' parameter to read CSV in parts [OK]

Common Mistakes:

• Using 'chunk' instead of 'chunksize'
• Using 'size' or 'batch' which are invalid
• Forgetting to specify chunk size

3. What will be the output of the following code snippet?

import pandas as pd
import numpy as np

df = pd.DataFrame({
    'A': np.random.randint(0, 100, 5),
    'B': ['cat', 'dog', 'cat', 'dog', 'cat']
})
df['B'] = df['B'].astype('category')
print(df.memory_usage(deep=True))

medium

A. Raises a TypeError due to invalid astype conversion

B. Prints the DataFrame instead of memory usage

C. Shows memory usage with 'B' column using more memory than object type

D. Shows memory usage with 'B' column using less memory than object type

Solution

1. Step 1: Understand astype('category') effect

   Converting column 'B' to category reduces memory by storing unique values once.

2. Step 2: Interpret memory_usage(deep=True)

   This method shows memory used by each column including actual string data size.

3. Final Answer:

   Shows memory usage with 'B' column using less memory than object type -> Option D

4. Quick Check:

   Category type reduces memory usage [OK]

Hint: astype('category') lowers memory for repeated text columns [OK]

Common Mistakes:

• Expecting error from astype conversion
• Thinking category uses more memory
• Confusing print output with DataFrame display

4. Identify the error in the following code that attempts to reduce memory usage:

import pandas as pd

df = pd.read_csv('data.csv')
df['col'] = df['col'].astype('category')
df = df.astype({'num_col': 'int8'})
print(df.memory_usage())

medium

A. Using 'int8' may cause overflow if values exceed range

B. memory_usage() does not show memory savings

C. astype cannot convert columns after reading CSV

D. No error; code correctly reduces memory usage

Solution

1. Step 1: Check int8 range suitability

   int8 supports values from -128 to 127; larger values cause overflow.

2. Step 2: Identify potential overflow risk

   If 'num_col' has values outside int8 range, conversion causes incorrect data.

3. Final Answer:

   Using 'int8' may cause overflow if values exceed range -> Option A

4. Quick Check:

   int8 range limits can cause data errors [OK]

Hint: Check numeric ranges before downcasting to smaller types [OK]

Common Mistakes:

• Assuming all int conversions are safe
• Believing memory_usage() ignores changes
• Thinking astype fails after CSV read

5. You have a large dataset with a column 'status' containing only three unique string values repeated many times. Which memory-efficient approach is best to reduce memory usage and why? Options: A) Drop the 'status' column to save memory. B) Convert 'status' to string type and keep numeric columns as float64. C) Convert 'status' to category type and downcast numeric columns to smallest possible integer type. D) Convert all columns to object type for flexibility.

hard

A. Drop the 'status' column to save memory.

B. Convert 'status' to category type and downcast numeric columns to smallest possible integer type.

C. Convert 'status' to string type and keep numeric columns as float64.

D. Convert all columns to object type for flexibility.

Solution

1. Step 1: Use category for repeated strings

   Converting 'status' to category stores unique values once, saving memory.

2. Step 2: Downcast numeric columns

   Downcasting numeric columns to smallest integer type reduces memory without losing data.

3. Step 3: Evaluate other options

   Keeping strings as object or dropping columns wastes memory or data; object type uses more memory.

4. Final Answer:

   Convert 'status' to category type and downcast numeric columns to smallest possible integer type. -> Option B

5. Quick Check:

   Category + downcast = best memory saving [OK]

Hint: Use category for repeated strings and downcast numbers [OK]

Common Mistakes:

• Dropping useful columns unnecessarily
• Keeping strings as object wastes memory
• Converting all to object increases memory