Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

GPU available but not used

See original GitHub issue

Executing CFLOW model on Colab, PyTorch returns this

GPU available: True, used: False
TPU available: False, using: 0 TPU cores
IPU available: False, using: 0 IPUs
HPU available: False, using: 0 HPUs

GPU available but not used. Set "accelerator" and "devices" using Trainer(accelerator='gpu', devices=1).

Even if i’m setting gpus=1 on the config.yml of cflow.

To Reproduce train.py --model cflow

GPU Model GPU 0: Tesla T4

Versions

pytorch-lightning             1.6.1
torch                         1.10.0+cu111
torchaudio                    0.10.0+cu111
torchmetrics                  0.7.3
torchsummary                  1.5.1
torchtext                     0.11.0
torchvision                   0.11.1+cu111

Issue Analytics

State:
Created a year ago
Comments:12 (4 by maintainers)

Top GitHub Comments

1reaction

andriy-onufriyenkocommented, Apr 15, 2022

I solved rolling back at version of pytorch-lightning==1.5.9

I found the problem. PyTorch Lightning deprecated and / or modified some of the Trainer configs after v1.6.0, which is the reason for not using the GPU despite being available.

The issue has been fixed in PR #234

@samet-akcay

I checked it works for me:

GPU available: True, used: True
TPU available: False, using: 0 TPU cores
IPU available: False, using: 0 IPUs
HPU available: False, using: 0 HPUs

Just replace all 11 files from PR 234 in to my project.

0reactions

samet-akcaycommented, Apr 14, 2022

I solved rolling back at version of pytorch-lightning==1.5.9

I found the problem. PyTorch Lightning deprecated and / or modified some of the Trainer configs after v1.6.0, which is the reason for not using the GPU despite being available.

The issue has been fixed in PR #234