google-deepmind / google-deepmind/dm_pix
Gaussian blur cpu performance
- Dominant language
- Python
- Stars
- 448
- Forks
- 31
- Avg merge
- 1d 55m
- Merged PRs (30d)
- 5
Description
I have been doing some experiments with PIX since it allows computing image augmentations in the GPU in contrast to torchvision which computes in the CPU and requires multiple workers to avoid bottlenecks. When performing some very simple `timeit` examples I observed a very high time when performing a gaussian blur in the CPU. I created a simple [Colab notebook](https://colab.research.google.com/drive/1UgqZVW2I09pPia2EZKhsZTnvwvucRu3Z?usp=sharing ) to demonstrate these experiments. I even tested transferring the image to CPU before performing the blur but it doesn't seem to make any difference. I was wondering if this is intended and I should not rely on CPU computations at all or if something is yet to be optimized for CPU computation.
Contributor guide
Assessment
This issue has not been assessed yet.