Understanding array memory layout in NumPy

Introduction

Knowing how arrays are stored in memory helps you understand how fast your code runs and how data is accessed.

When you want to speed up your data processing by using efficient memory access.

When you need to share data between programs without copying it.

When you want to reshape or slice arrays without making extra copies.

When debugging unexpected behavior related to data changes in arrays.

When working with large datasets and want to save memory.

Syntax

NumPy

import numpy as np

# Create a numpy array
array = np.array([[1, 2, 3], [4, 5, 6]])

# Check if array is stored in C-contiguous order (row-major)
is_c_contiguous = array.flags['C_CONTIGUOUS']

# Check if array is stored in Fortran-contiguous order (column-major)
is_f_contiguous = array.flags['F_CONTIGUOUS']

# Get the memory layout strides (steps in bytes to move to next element in each dimension)
strides = array.strides

C-contiguous means rows are stored one after another in memory.

Fortran-contiguous means columns are stored one after another in memory.

Examples

Even empty arrays are considered contiguous in memory.

NumPy

import numpy as np

# Empty array
empty_array = np.array([])
print(empty_array.flags['C_CONTIGUOUS'])  # True because empty arrays are trivially contiguous

Single element arrays are also contiguous and strides show how memory moves.

NumPy

import numpy as np

# One element array
one_element_array = np.array([42])
print(one_element_array.flags['C_CONTIGUOUS'])  # True
print(one_element_array.strides)  # Shows the byte step size

Transposing changes the memory layout from row-major to column-major.

NumPy

import numpy as np

# Transposed array changes memory layout
array = np.array([[1, 2, 3], [4, 5, 6]])
transposed_array = array.T
print(transposed_array.flags['C_CONTIGUOUS'])  # Usually False
print(transposed_array.flags['F_CONTIGUOUS'])  # Usually True

Slicing with steps can create arrays that are not contiguous in memory.

NumPy

import numpy as np

# Slicing may create non-contiguous views
array = np.arange(10)
sliced_array = array[::2]
print(sliced_array.flags['C_CONTIGUOUS'])  # Usually False
print(sliced_array.strides)

Sample Program

This program shows how a numpy array is stored in memory, how transposing changes the layout, and how slicing affects contiguity.

NumPy

import numpy as np

# Create a 2D array
array = np.array([[10, 20, 30], [40, 50, 60]])

print("Original array:")
print(array)

# Check memory layout flags
print("Is C-contiguous?", array.flags['C_CONTIGUOUS'])
print("Is Fortran-contiguous?", array.flags['F_CONTIGUOUS'])
print("Strides:", array.strides)

# Transpose the array
transposed_array = array.T
print("\nTransposed array:")
print(transposed_array)

print("Is C-contiguous?", transposed_array.flags['C_CONTIGUOUS'])
print("Is Fortran-contiguous?", transposed_array.flags['F_CONTIGUOUS'])
print("Strides:", transposed_array.strides)

# Slice the original array with step
sliced_array = array[:, ::2]
print("\nSliced array (every second column):")
print(sliced_array)

print("Is C-contiguous?", sliced_array.flags['C_CONTIGUOUS'])
print("Is Fortran-contiguous?", sliced_array.flags['F_CONTIGUOUS'])
print("Strides:", sliced_array.strides)

Important Notes

Time complexity: Checking memory layout flags is very fast (constant time).

Space complexity: No extra memory is used when checking flags or strides.

Common mistake: Assuming all numpy arrays are stored row-wise (C-contiguous). Transposed or sliced arrays may not be.

Use this knowledge when you want to optimize performance or avoid unexpected data copies.

Summary

Arrays can be stored in memory in different orders: row-major (C-contiguous) or column-major (Fortran-contiguous).

Transposing or slicing arrays can change their memory layout and contiguity.

Understanding memory layout helps write faster and more memory-efficient code.

Practice

1. What does it mean when a NumPy array is C-contiguous?

easy

A. The array is stored as a list of Python objects.

B. The array is stored in column-major order, meaning columns are stored one after another in memory.

C. The array is stored in row-major order, meaning rows are stored one after another in memory.

D. The array is stored in a compressed format to save memory.

Solution

1. Step 1: Understand memory layout types

   C-contiguous means the array is stored in row-major order, where rows are stored sequentially in memory.

2. Step 2: Compare with other layouts

   Fortran-contiguous arrays store columns sequentially, not rows.

3. Final Answer:

   The array is stored in row-major order, meaning rows are stored one after another in memory. -> Option C

4. Quick Check:

   C-contiguous = row-major order [OK]

Hint: C-contiguous means rows stored sequentially in memory [OK]

Common Mistakes:

• Confusing C-contiguous with Fortran-contiguous
• Thinking C-contiguous means compressed storage
• Assuming C-contiguous means column-major order

2. Which of the following NumPy commands correctly checks if an array a is stored in Fortran-contiguous order?

easy

A. np.isfortran(a)

B. np.iscontiguous(a)

C. a.is_fortran()

D. a.flags.f_contiguous

Solution

1. Step 1: Recall NumPy flags for memory layout

   NumPy arrays have a flags attribute with f_contiguous to check Fortran order.

2. Step 2: Identify correct syntax

   a.flags.f_contiguous returns True if array a is Fortran-contiguous.

3. Final Answer:

   a.flags.f_contiguous -> Option D

4. Quick Check:

   Check Fortran order with a.flags.f_contiguous [OK]

Hint: Use a.flags.f_contiguous to check Fortran order [OK]

Common Mistakes:

• Using non-existent functions like np.isfortran
• Confusing C-contiguous and Fortran-contiguous flags
• Trying to call methods that don't exist on arrays

3. Consider the following code:

import numpy as np
arr = np.array([[1, 2, 3], [4, 5, 6]])
transposed = arr.T
print(transposed.flags.c_contiguous)

What will be the output?

medium

A. True

B. False

C. Raises an AttributeError

D. None

Solution

1. Step 1: Understand the original array layout

   Original array arr is C-contiguous by default (row-major).

2. Step 2: Analyze the transpose operation

   Transposing arr.T changes memory layout to non-C-contiguous because rows and columns swap.

3. Step 3: Check the flag after transpose

   transposed.flags.c_contiguous will be False since the transpose breaks row-major order.

4. Final Answer:

   False -> Option B

5. Quick Check:

   Transpose breaks C-contiguity = False [OK]

Hint: Transpose usually breaks C-contiguity, so flag is False [OK]

Common Mistakes:

• Assuming transpose keeps C-contiguity True
• Confusing c_contiguous with f_contiguous
• Expecting an error instead of a boolean

4. You have this code:

import numpy as np
arr = np.arange(6).reshape(2, 3)
sliced = arr[:, 1:3]
print(sliced.flags.c_contiguous)

Why might sliced.flags.c_contiguous be False?

medium

A. Because slicing can create views that are not stored continuously in memory.

B. Because slicing always returns a copy, which is never contiguous.

C. Because reshape changes the memory layout to Fortran order.

D. Because arange creates arrays that are never contiguous.

Solution

1. Step 1: Understand slicing behavior

   Slicing often returns a view, which may not be stored continuously in memory.

2. Step 2: Check memory layout after slicing

   The slice arr[:, 1:3] selects columns 1 and 2, which may not be contiguous in row-major order.

3. Step 3: Explain why c_contiguous is False

   Because the slice skips some elements in memory, the resulting view is not C-contiguous.

4. Final Answer:

   Because slicing can create views that are not stored continuously in memory. -> Option A

5. Quick Check:

   Slicing can break contiguity = False [OK]

Hint: Slicing can create non-contiguous views, so flag may be False [OK]

Common Mistakes:

• Thinking slicing always returns a copy
• Assuming reshape changes memory layout to Fortran order by default
• Believing arange arrays are never contiguous

5. You want to create a large 2D NumPy array with shape (1000, 1000) that is stored in Fortran order for faster column-wise operations. Which code snippet correctly creates such an array?

hard

A. np.zeros((1000, 1000), order='F')

B. np.zeros((1000, 1000), order='C')

C. np.zeros((1000, 1000)).T.copy()

D. np.zeros((1000, 1000), fortran=True)

Solution

1. Step 1: Recall how to specify memory order in NumPy

   Use the order parameter with value 'F' to create Fortran-contiguous arrays.

2. Step 2: Analyze each option

   np.zeros((1000, 1000), order='F') uses order='F', which is correct. np.zeros((1000, 1000), order='C') uses 'C' (row-major). np.zeros((1000, 1000)).T.copy() transposes a C-contiguous array and copies it into a new C-contiguous array by default. np.zeros((1000, 1000), fortran=True) uses an invalid parameter.

3. Final Answer:

   np.zeros((1000, 1000), order='F') -> Option A

4. Quick Check:

   Use order='F' to create Fortran order arrays [OK]

Hint: Use order='F' in array creation for Fortran order [OK]

Common Mistakes:

• Using order='C' instead of 'F'
• Trying to transpose to get Fortran order
• Using invalid parameters like fortran=True