3 ms·
"The most powerful GPU currently available is the NVIDIA Tesla K80 Accelerator, with up to 8.74 teraflops of compute performance and nearly 500 GB/sec of memory
by joe_the_user 11y ago
"The most powerful GPU currently available is the NVIDIA Tesla K80 Accelerator, with up to 8.74 teraflops of compute performance and nearly 500 GB/sec of memory bandwidth."
Wow, I've been reading, on Nvidia's site and elsewhere, about cuda programming on gpus and a lot of the advice involves avoiding a lot of transfers between main memory and the gpu. However, at the transfer rate quoted above, it seems like you have a device that can read all of main memory in a few seconds.
This is great ... however, does this mean all the advice about avoiding memory transfers and the programming style went with that, goes out the window?
Edit: as a beginner, I'm probably butchering the standard advice for c++/cuda programming. However, could someone summarize how things change as you get to more capable processors. A lot of the Nvidia blog posts are geared to stuff valid for all cuda version but since I'm starting fresh with a compute-intense program targeting cuda, I'd like to target the best things cuda can do.
Edit2: While the article is fascinating for the possibilities it's talking about, it's mostly a puff-piece for some (apparently) closed-source software. Anyone know an open source equivalent or some more detailed sample code for doing stuff similar to what MapD claims to do?
- robbies 11y agoThat 500 GB/s is the bandwidth between the NV shader cores and the GPU RAM, not between the shader cores and CPU accessible system RAM. You don't want to be transferring between the two pools that often, as those buses are much slower.
- pmalynin 11y agoYeah, RAM AFAIK is about 22 GB/s
- trsohmers 11y agoAnd PCIe Gen 3 is limited to 16GB/s, which is the real bottleneck between the CPU and GPU... if you can use all 16 lanes. Most GPGPU set ups with multiple GPUs only are able to use 4 or 8 lanes each, so you then are stuck with multiple 4 or 8GB/s bottlenecks.