[larodi]

Indeed, has anyone so far successfully drop-in replaced numpy in a project with this cupy and achieved massive improvements? Because, you know, when dealing with GPU it is very important to actually understand how data flows back and forth to it, not only the algorithmic nature of the code written.

As a sidenote, it is funny how this gets released in 2024, and not in say 2014...

[KeplerBoy]

Oh yes, I've personally used CuPy for great speed ups compared to Numpy in radar signal processing. Taking a code that took 30 seconds with NumPy down to 1 second with CuPy. The code basically performed a bunch of math on like 100 MB of data, so the PCIe bottleneck was not a big issue.

Also CuPy was first released in 2015, this post is just a reminder for people that such things exist.

[larodi]

Thank you. Your post is informative, and well grounds the very inappropriate hype in mine.

[lacker]

Yeah, the data managed by cupy generally stays on the GPU and you can control when you get it out pretty straightforwardly. It’s great if most of your work happens in a small number of standard operations. Like matrix operations or Fourier transforms, the sort of thing that cupy will provide for you. You can get custom kernels running through cupy but at some point it’s easier to just write c/c++.

[faangguyindia]

It's because it was not possible to write tons of brain-dead, repetitive code in 2014.

In 2024, with AI you can do these kind of projects very fast.