Gradient accumulation in PyTorch - Model Pipeline Trace

Model Pipeline - Gradient accumulation

This pipeline shows how gradient accumulation helps train a model with small batches by adding gradients over multiple steps before updating the model weights.

Data Flow - 5 Stages

1Data loading

1000 rows x 10 features→Load dataset and prepare batches of size 4→1000 rows x 10 features (batched as 250 batches of 4 rows each)

[[0.5, 1.2, ..., 0.3], [0.1, 0.4, ..., 0.7], ...] (4 samples per batch)

↓

2Model input

4 rows x 10 features→Feed batch to model→4 rows x 1 output (logits)

[[0.7], [0.2], [0.9], [0.1]]

↓

3Loss calculation

4 rows x 1 output→Calculate loss for batch→Scalar loss value

Loss = 0.45

↓

4Gradient accumulation

Gradients from batch of 4→Accumulate gradients over 4 batches (total 16 samples)→Accumulated gradients for 16 samples

Sum of gradients from 4 batches

↓

5Model update

Accumulated gradients→Update model weights once after 4 batches→Updated model weights

Weights adjusted after accumulated gradients

Training Trace - Epoch by Epoch

Loss
1.0 |*       
0.8 | **     
0.6 |  ***   
0.4 |    ****
0.2 |     ***
    +--------
     1 2 3 4 5 Epochs

Epoch	Loss ↓	Accuracy ↑	Observation
1	0.85	0.60	Loss starts high, accuracy moderate
2	0.65	0.72	Loss decreases, accuracy improves
3	0.50	0.80	Loss continues to decrease, accuracy rises
4	0.40	0.85	Model converging well
5	0.35	0.88	Loss low, accuracy high

Prediction Trace - 6 Layers

Layer 1: Input batch

Layer 2: Forward pass

Layer 3: Loss calculation

Layer 4: Backward pass

Layer 5: Gradient accumulation

Layer 6: Optimizer step

Model Quiz - 3 Questions

Why do we accumulate gradients over multiple batches before updating weights?

A To simulate a larger batch size and reduce memory usage

B To increase the learning rate automatically

C To avoid calculating gradients

D To skip the backward pass

Key Insight

Gradient accumulation allows training with effectively larger batch sizes without needing more memory. It sums gradients over several small batches before updating weights, helping models train efficiently on limited hardware.

Practice

1. What is the main purpose of gradient accumulation in PyTorch training?

easy

A. To reduce the number of model parameters

B. To increase the learning rate automatically

C. To change the model architecture dynamically

D. To split a large batch into smaller steps to save memory

Solution

1. Step 1: Understand gradient accumulation concept

   Gradient accumulation splits a large batch into smaller mini-batches to avoid memory overflow.

2. Step 2: Identify the main benefit

   This technique helps save GPU memory by processing smaller batches sequentially before updating weights.

3. Final Answer:

   To split a large batch into smaller steps to save memory -> Option D

4. Quick Check:

   Gradient accumulation = batch splitting for memory saving [OK]

Hint: Gradient accumulation saves memory by splitting batches [OK]

Common Mistakes:

• Thinking it changes learning rate
• Confusing with model size reduction
• Assuming it alters model layers

2. Which PyTorch code snippet correctly implements gradient accumulation over 4 steps?

easy

A. for i, data in enumerate(dataloader):
outputs = model(data)
loss = criterion(outputs, labels)
optimizer.step()
loss.backward()
optimizer.zero_grad()

B. for i, data in enumerate(dataloader):
outputs = model(data)
loss = criterion(outputs, labels)
loss.backward()
optimizer.step()
if (i + 1) % 4 == 0:
optimizer.zero_grad()

C. for i, data in enumerate(dataloader):
outputs = model(data)
loss = criterion(outputs, labels)
loss.backward()
if (i + 1) % 4 == 0:
optimizer.step()
optimizer.zero_grad()

D. for i, data in enumerate(dataloader):
outputs = model(data)
loss = criterion(outputs, labels)
optimizer.zero_grad()
loss.backward()
if (i + 1) % 4 == 0:
optimizer.step()

Solution

1. Step 1: Identify correct order of operations

   Gradient accumulation requires calling loss.backward() each step, then optimizer.step() and zero_grad() after accumulating gradients.

2. Step 2: Check modulo condition for accumulation

   Only after 4 mini-batches (i+1 % 4 == 0) should optimizer.step() and zero_grad() be called to update weights and reset gradients.

3. Final Answer:

   Code that calls loss.backward() every step and optimizer.step() plus zero_grad() every 4 steps -> Option C

4. Quick Check:

   Backward every step, step and zero_grad every 4 steps [OK]

Hint: Call backward every step, step and zero_grad every N steps [OK]

Common Mistakes:

• Calling optimizer.step() before loss.backward()
• Resetting gradients too early
• Not using modulo condition correctly

3. Given this PyTorch code with gradient accumulation steps=2, what is the printed loss after 4 batches?

optimizer.zero_grad()
for i, (inputs, labels) in enumerate(dataloader):
    outputs = model(inputs)
    loss = criterion(outputs, labels) / 2
    loss.backward()
    if (i + 1) % 2 == 0:
        optimizer.step()
        optimizer.zero_grad()
    print(f"Batch {i+1} loss: {loss.item()}")

medium

A. Loss values cause runtime error due to division

B. Loss values divided by 2 printed for each batch

C. Loss values accumulated and printed only every 2 batches

D. Loss values printed without division

Solution

1. Step 1: Understand loss scaling in code

   Loss is divided by 2 before backward to average gradients over 2 accumulation steps.

2. Step 2: Check print statement inside loop

   Loss.item() prints the scaled loss for each batch, so printed values are divided by 2 every batch.

3. Final Answer:

   Loss values divided by 2 printed for each batch -> Option B

4. Quick Check:

   Loss scaled by 2 and printed each batch [OK]

Hint: Loss is scaled before backward, printed as scaled every batch [OK]

Common Mistakes:

• Thinking loss prints only every 2 batches
• Ignoring loss division by 2
• Assuming runtime error from division

4. Identify the error in this gradient accumulation code snippet:

optimizer.zero_grad()
for i, (inputs, labels) in enumerate(dataloader):
    outputs = model(inputs)
    loss = criterion(outputs, labels)
    loss.backward()
    if i % 4 == 0:
        optimizer.step()
        optimizer.zero_grad()

medium

A. optimizer.step() and zero_grad() are called too early at i=0

B. loss.backward() is missing gradient scaling

C. optimizer.zero_grad() should be called before loss.backward()

D. The loop should use (i + 1) % 4 == 0 instead of i % 4 == 0

Solution

1. Step 1: Analyze the modulo condition

   Condition i % 4 == 0 triggers optimizer.step() and zero_grad() at i=0, which is before any gradients accumulate.

2. Step 2: Understand correct timing for optimizer step

   Optimizer step should happen after 4 batches, so condition should be (i + 1) % 4 == 0 to avoid early update.

3. Final Answer:

   optimizer.step() and zero_grad() are called too early at i=0 -> Option A

4. Quick Check:

   Modulo condition triggers step too early [OK]

Hint: Use (i + 1) % N == 0 to delay step until after N batches [OK]

Common Mistakes:

• Calling optimizer.step() at first batch
• Confusing zero_grad() timing
• Ignoring off-by-one in modulo condition

5. You want to train a large model on a GPU with limited memory using gradient accumulation with batch size 64 split into 8 steps. Which approach correctly adjusts the learning rate and loss scaling to keep training stable?

hard

A. Divide the loss by 8 before backward and keep the original learning rate

B. Multiply the learning rate by 8 and do not scale the loss

C. Divide the learning rate by 8 and multiply the loss by 8

D. Keep loss and learning rate unchanged, just accumulate gradients

Solution

1. Step 1: Understand gradient accumulation effect on loss

   Splitting batch into 8 steps means gradients accumulate over 8 mini-batches, so loss must be divided by 8 to average gradients correctly.

2. Step 2: Adjust learning rate accordingly

   Learning rate stays the same because gradient accumulation simulates a larger batch size without changing optimization dynamics.

3. Final Answer:

   Divide the loss by 8 before backward and keep the original learning rate -> Option A

4. Quick Check:

   Loss scaled down, learning rate unchanged for stable accumulation [OK]

Hint: Scale loss down by steps, keep learning rate same [OK]

Common Mistakes:

• Scaling learning rate instead of loss
• Not scaling loss causing gradient explosion
• Assuming no changes needed for accumulation