You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The transforms in mmcv.image.geometric.py make many calls to opencv that appear to not leverage CUDA. For example, cv2.warpAffine is called here. This operation is just a matrix multiplication, which are massively accelerated by leveraging a GPU over a CPU. It not using the GPU is creating a bottleneck in my current training pipeline.
Does anyone know why CUDA isn't used or if I'm missing something? I would imagine this would massively accelerate the data augmentations in many people's training pipelines immediately.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
The transforms in
mmcv.image.geometric.py
make many calls to opencv that appear to not leverage CUDA. For example,cv2.warpAffine
is called here. This operation is just a matrix multiplication, which are massively accelerated by leveraging a GPU over a CPU. It not using the GPU is creating a bottleneck in my current training pipeline.Does anyone know why CUDA isn't used or if I'm missing something? I would imagine this would massively accelerate the data augmentations in many people's training pipelines immediately.
Beta Was this translation helpful? Give feedback.
All reactions