Lightning-AI / Lightning-AI/pytorch-lightning

Multi-gpu training is much lower than single gpu (due to additional processes?)

Open
#19,796 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug distributed strategy: deepspeed ver: 2.1.x
Dominant language
Python
Stars
31.4k
Forks
3.8k
Avg merge
6d 7h
Merged PRs (30d)
6

Description

Bug description

I use DeepSpeed ZeRO Stage 2 Offload integrated in lightning to train my model. When I use single gpu, the training time for one epoch is about 5h. However, When I use two ranks, the time extends to about 12.5h.
Something strange is that when I use single gpu, there is only one process by checking nvidia-smi, while it becomes two processes on each rank for 2-gpu training.
If I use large batch size, it will report Out of CUDA memory error and exit. For single-gpu, the training just terminated. However, for 2-gpu, only one process on each rank exits and the remaining one is still running, after that the training continues normally with much faster speed (2.5h/epoch), which seems to be the desired speed (half of what with single-gpu).
It looks that the additional process limits the speed of multi-gpu training. Is its existence normal? If so, what's its function? Is there anyway to avoid it? (Obviously I don't want to exit it by making Out of CUDA memory error manually.)

What version are you seeing the problem on?

v2.1

How to reproduce the bug
trainer = Trainer(devices=[0,1],  # for single-gpu: 1
                  accelerator="gpu",
                  callbacks=[epoch_end_callback, checkpoint_callback, earlystop_callback],
                  min_epochs=min_epoch,
                  max_epochs=max_epoch,
                  deterministic=True,
                  benchmark=True,
                  strategy='deepspeed_stage_2_offload',
                  logger=logger,
                  profiler='simple'
                  )

Optimizer: `deepspeed.ops.adam.DeepSpeedCPUAdam`
Error messages and logs

2-gpu:
image
single-gpu:
image

Environment
Current environment
#- Lightning Component (e.g. Trainer, LightningModule, LightningApp, LightningWork, LightningFlow): Trainer
#- PyTorch Lightning Version (e.g., 1.5.0): 2.1.3
#- PyTorch Version (e.g., 2.0): 2.0.1
#- Python version (e.g., 3.9): 3.10.12
#- OS (e.g., Linux): CentOS Linux release 7.4.1708 (Core)
#- CUDA/cuDNN version: CUDA 11.7 + cuDNN 8.5
#- GPU models and configuration: 2 ranks in one A40 GPU
#- How you installed Lightning(`conda`, `pip`, source): conda
More info

No response

cc @justusschock @lantiga

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reported Trainer configuration using devices=[0,1], accelerator="gpu", and strategy='deepspeed_stage_2_offload', then compare process counts and epoch times against single-GPU training. The issue does not name source files or tests; done would require identifying the extra processes' purpose and explaining or correcting the multi-GPU slowdown and memory behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
distributed-systems, machine-learning
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.