Skip to content

README.md multi-GPU training instructions add bold emphasis to how numGPUs influences batch size #268

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from
+1 −1
Open

README.md multi-GPU training instructions add bold emphasis to how numGPUs influences batch size #268

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -511,7 +511,7 @@ You can fine-tune RF-DETR on multiple GPUs using PyTorch’s Distributed Data Pa
python -m torch.distributed.launch --nproc_per_node=8 --use_env main.py
```

Replace `8` in the `--nproc_per_node argument` with the number of GPUs you want to use. This approach creates one training process per GPU and splits the workload automatically. Note that your effective batch size is multiplied by the number of GPUs, so you may need to adjust your `batch_size` and `grad_accum_steps` to maintain the same overall batch size.
Replace `8` in the `--nproc_per_node argument` with the number of GPUs you want to use. This approach creates one training process per GPU and splits the workload automatically. **Note that your effective batch size is multiplied by the number of GPUs**, so **you may need to adjust your `batch_size` and `grad_accum_steps` to maintain the same overall batch size!**

### Result checkpoints

Expand Down