Skip to content
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.

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

GPU utilization is low when training on COCO dataset #9929

Closed
1 task done
ice-tall-cold opened this issue Oct 26, 2022 · 7 comments
Closed
1 task done

GPU utilization is low when training on COCO dataset #9929

ice-tall-cold opened this issue Oct 26, 2022 · 7 comments
Labels
question Further information is requested Stale

Comments

@ice-tall-cold
Copy link

Search before asking

Question

Hi,
I'm using 3090ti to train yolov5s. When I train with COCO128, it's pretty fast and GPU utilization is high. But when I train with COCO dataset, it's much slower and GPU utilization is also low. I search on the website and realize it might be that the data read speed is low and GPU is always waiting. Then I use the new SSD and it increases the training speed and GPU utilization a little. But it still takes one and a half hours to train one epoch. Do you know what else I can do to further increase the training speed and GPU utilization? Appreciate it if you can provide any advice.

Additional

No response

@ice-tall-cold ice-tall-cold added the question Further information is requested label Oct 26, 2022
@github-actions
Copy link
Contributor

github-actions bot commented Oct 26, 2022

👋 Hello @ice-tall-cold, thank you for your interest in YOLOv5 🚀! Please visit our ⭐️ Tutorials to get started, where you can find quickstart guides for simple tasks like Custom Data Training all the way to advanced concepts like Hyperparameter Evolution.

If this is a 🐛 Bug Report, please provide screenshots and minimum viable code to reproduce your issue, otherwise we can not help you.

If this is a custom training ❓ Question, please provide as much information as possible, including dataset images, training logs, screenshots, and a public link to online W&B logging if available.

For business inquiries or professional support requests please visit https://ultralytics.com or email support@ultralytics.com.

Requirements

Python>=3.7.0 with all requirements.txt installed including PyTorch>=1.7. To get started:

git clone https://github.com/ultralytics/yolov5  # clone
cd yolov5
pip install -r requirements.txt  # install

Environments

YOLOv5 may be run in any of the following up-to-date verified environments (with all dependencies including CUDA/CUDNN, Python and PyTorch preinstalled):

Status

YOLOv5 CI

If this badge is green, all YOLOv5 GitHub Actions Continuous Integration (CI) tests are currently passing. CI tests verify correct operation of YOLOv5 training, validation, inference, export and benchmarks on MacOS, Windows, and Ubuntu every 24 hours and on every commit.

@ice-tall-cold
Copy link
Author

And I already train on cached data and tried increasing the batch size.

@glenn-jocher
Copy link
Member

glenn-jocher commented Oct 26, 2022

👋 Hello! Thanks for asking about training speed issues. YOLOv5 🚀 can be trained on CPU (slowest), single-GPU, or multi-GPU (fastest). If you would like to increase your training speed some options are:

  • Increase --batch-size
  • Reduce --img-size
  • Reduce model size, i.e. from YOLOv5x -> YOLOv5l -> YOLOv5m -> YOLOv5s
  • Train with multi-GPU DDP at larger --batch-size
  • Train on cached data: python train.py --cache (RAM caching) or --cache disk (disk caching)
  • Train on faster GPUs, i.e.: P100 -> V100 -> A100
  • Train on free GPU backends with up to 16GB of CUDA memory: Open In Colab Open In Kaggle

Good luck 🍀 and let us know if you have any other questions!

@MartinPedersenpp
Copy link

What is your batch size?

@ice-tall-cold
Copy link
Author

What is your batch size?

Now I'm using 64. And it gets better than before.

@github-actions
Copy link
Contributor

github-actions bot commented Nov 27, 2022

👋 Hello, this issue has been automatically marked as stale because it has not had recent activity. Please note it will be closed if no further activity occurs.

Access additional YOLOv5 🚀 resources:

Access additional Ultralytics ⚡ resources:

Feel free to inform us of any other issues you discover or feature requests that come to mind in the future. Pull Requests (PRs) are also always welcomed!

Thank you for your contributions to YOLOv5 🚀 and Vision AI ⭐!

@github-actions github-actions bot added the Stale label Nov 27, 2022
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 7, 2022
@glenn-jocher
Copy link
Member

@ice-tall-cold glad to hear that increasing the batch size has improved the training speed! 🚀 Larger batch sizes can often help utilize the GPU more efficiently. If you have any more questions or need further assistance, feel free to ask!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested Stale
Projects
None yet
Development

No branches or pull requests

3 participants