CUDA

Multiple hardware-specific issues affect PyTorch across different backends: LayerNorm/BatchNorm fail to compile on Apple M4 MPS, Conv2d is slower on macOS without MKLDNN, CUDA CI tests exhibit memory corruption (SIGIOT), and ONNX exports with dynamic inputs regressed between versions. These issues require constant per-platform debugging.

Developers must manually align PyTorch, CUDA toolkit, and Python versions to enable GPU acceleration. Mismatches produce cryptic errors like 'Torch not compiled with CUDA enabled,' and newcomers unfamiliar with CUDA can spend significant time debugging installation issues.

Using cudaMallocManaged (UVM) in PyTorch workloads leads to costly double-transfer overhead when GPU memory is full — pages are evicted to CPU and re-fetched, effectively halving memory bandwidth. Explicit memory placement consistently outperforms UVM for typical deep learning workloads.

GPU acceleration support in Java requires extra setup and tuning compared to Python, and forcing GPU allocation per application instance (even when idle) creates scaling and maintenance challenges with higher infrastructure costs and lower resource efficiency.

TensorFlow attempts to allocate all available GPU memory on startup, which can prevent other code from accessing the same hardware and limits flexibility in local development environments where developers want to allocate portions of GPU to different tasks.

TensorFlow only supports NVIDIA GPUs and Python for GPU programming with no additional support for other accelerators, limiting cross-platform development flexibility.