We value your privacy

We use cookies to enhance your browsing experience, serve personalized ads or content, and analyze our traffic. By clicking "Accept All", you consent to our use of cookies.

Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Skip to content

CUDA

Runtime vs.number of dataloader workers and batch size

PyTorch / datasets / dataloader / data transfer to GPU – II – dataloader too slow on CPU?

In the last post of this mini-series we saw that some Pytorch torchvision datasets have a directly accessible property “data“. There we find image data in a dataset specific format. In the case of MNIST and FashionMNIST (and for many other sets) these data are already torch tensors. However, due to the fact that these tensors are squeezed, they do… Read More »PyTorch / datasets / dataloader / data transfer to GPU – II – dataloader too slow on CPU?

CUDA and cudnn with Pytorch and Tensorflow in one virtual Python environment on your Linux system

One of the problems I recently ran into was the coexistence of Tensorflow2 [TF2] and PyTorch in the very same virtual Python environment. I just wanted to make experiments to compare the performance of some Keras-based models with the TF2-backend on one side and, on the other side, with the PyTorch-backend. My trouble resulted from a mismatch of two CUDA/cudnn… Read More »CUDA and cudnn with Pytorch and Tensorflow in one virtual Python environment on your Linux system

Setting NUMA node to 0 for Nvidia cards on standard Linux PCs

People working on Linux PCs with Tensorflow 2 [TF2] and CUDA may be confronted with warnings complaining a lack of an assignment of their Nvidia graphics card to a NUMA node. This is somewhat enervating as depending on the TF2 version a default entry of “-1” for the NUMA on consumer systems may clatter some of your Jupyter notebook cells… Read More »Setting NUMA node to 0 for Nvidia cards on standard Linux PCs

Installation of CUDA 12.3 and CuDNN 8.9 on Opensuse Leap 15.5 for Machine Learning

Machine Learning on a Linux system is no fun without a GPU and its parallel processing capabilities. On a system with a Nvidia card you need basic Nvidia drivers and additional libraries for optimal support of Deep Neural Networks and Linear Algebra operations on the GPU sub-processors. E.g., Keras and Tensorflow 2 [TF2] use CUDA and cuDNN-libraries on your Nvidia… Read More »Installation of CUDA 12.3 and CuDNN 8.9 on Opensuse Leap 15.5 for Machine Learning