A data scientist loads a 40 GB dataset into GPU memory for columnar aggregations using cuDF, but the GPU has only 24 GB of VRAM. Which characteristic of GPU-accelerated data science most directly explains why this configuration will fail before any computation begins?
- AHigh memory bandwidth between CPU and GPU becomes a bottleneck when the PCIe transfer rate is slower than the dataset size.
- BGPU SIMT execution requires all threads to operate on data resident in VRAM, so the dataset must fit entirely in GPU memory before kernel dispatch. Correct
- CColumnar data layouts are padded to cache-line boundaries on the GPU, causing the effective memory footprint to exceed the raw dataset size by a fixed overhead.
- DcuDF requires a contiguous virtual address space spanning the entire dataset, and GPU address spaces are smaller than CPU address spaces on current hardware.
Why A is wrong: PCIe bandwidth is a throughput concern for data transfer, not the reason the configuration fails outright. A bandwidth bottleneck slows a successful computation; it does not prevent the operation from starting when the dataset exceeds VRAM capacity.
Why B is correct: GPU memory is the hard constraint in GPU-accelerated data science. SIMT (Single Instruction, Multiple Threads) execution means all active threads reference addresses in VRAM; there is no transparent spill to host RAM as with CPU virtualisation, so exceeding VRAM capacity causes an out-of-memory error before computation starts.
Why C is wrong: While columnar padding exists, it is a minor overhead and not the reason a 40 GB dataset cannot reside on a 24 GB GPU. The fundamental issue is that the raw dataset already exceeds total VRAM, making any padding discussion secondary and misleading here.
Why D is wrong: Modern GPU virtual address spaces are large and not the practical limiting factor. The actual limit is physical VRAM capacity, not virtual addressing. Citing address space size misleads a candidate into thinking a software or architecture limit causes the failure rather than the straightforward physical memory constraint.