deepspeedai / deepspeedai/DeepSpeedExamples

Step2: memory allocation of 2097152 bytes failed

Open
#321 4 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

bug deespeed chat
Dominant language
Python
Stars
6.8k
Forks
1.1k
Avg merge
2d 16h
Merged PRs (30d)
1

Description

when I run step2 using 'bash training_scripts/single_node/run_350m.sh' meet error

[2023-04-16 21:36:09,031] [INFO] [launch.py:235:main] nnodes=1, num_local_procs=8, node_rank=0
[2023-04-16 21:36:09,031] [INFO] [launch.py:246:main] global_rank_mapping=defaultdict(<class 'list'>, {'localhost': [0, 1, 2, 3, 4, 5, 6, 7]})
[2023-04-16 21:36:09,031] [INFO] [launch.py:247:main] dist_world_size=8
[2023-04-16 21:36:09,031] [INFO] [launch.py:249:main] Setting CUDA_VISIBLE_DEVICES=0,1,2,3,4,5,6,7
[2023-04-16 21:36:16,042] [INFO] [comm.py:586:init_distributed] Initializing TorchBackend in DeepSpeed with backend nccl
memory allocation of memory allocation of 20971522097152 bytes failed
 bytes failed
memory allocation of 2097152 bytes failed
[2023-04-16 21:54:13,235] [INFO] [launch.py:428:sigkill_handler] Killing subprocess 62215
[2023-04-16 21:54:16,017] [INFO] [launch.py:428:sigkill_handler] Killing subprocess 62216
[2023-04-16 21:54:16,029] [INFO] [launch.py:428:sigkill_handler] Killing subprocess 62217
[2023-04-16 21:54:18,477] [INFO] [launch.py:428:sigkill_handler] Killing subprocess 62218
[2023-04-16 21:54:21,046] [INFO] [launch.py:428:sigkill_handler] Killing subprocess 62219
[2023-04-16 21:54:21,057] [INFO] [launch.py:428:sigkill_handler] Killing subprocess 62220
[2023-04-16 21:54:21,060] [INFO] [launch.py:428:sigkill_handler] Killing subprocess 62221
[2023-04-16 21:54:23,710] [INFO] [launch.py:428:sigkill_handler] Killing subprocess 62222

I have already allocate 50g memory, but still failed

Contributor guide

No contributing guide indexed for this repository

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.