cupy VS bottleneck

I did not expect anything interesting, but this is actually cool.

> A full implementation of the NumPy API. Not something "NumPy-like" — just literally the NumPy API, with the same functions and the same arguments.

I suppose it's like https://cupy.dev/

What was the difference in runtime performance, and did you try CuPy?

https://github.com/cupy/cupy :

> CuPy is a NumPy/SciPy-compatible array library for GPU-accelerated computing with Python. CuPy acts as a drop-in replacement to run existing NumPy/SciPy code on NVIDIA CUDA or AMD ROCm platforms.

Projects using CuPy:

It's more effort though. You will likely have to format your data in specific ways for the GPU to efficiently process it. I've done this kind of thing with PyTorch tensors, but there are also math-specific libraries like CuPy. If you only have millions, Numpy should be fine.

I'd also recommend checking out CuPy which aims to fully re-implement the Numpy api for CUDA GPUs, while taking advantage of Nvidia's specialized libraries like cuBLAS, cuRAND, cuSOLVER etc. The tradeoff being that it only works with Nvidia GPUs.

u/Spataner's answer is great. If you WANT GPU-enabled numpy functions, I would check out CuPy: https://cupy.dev/

Not sure how VS Code is relevant here as it's just you IDE, shouldn't have any influence on this. Now, seeing as you're using numpy (which has no gpu support), you could try and use something like CuPy in place of numpy. I'm not sure about the interoperability because I've never used this myself, but if you're lucky it could be as simple as just replacing all numpy calls with the same CuPy calls (or replacing all import numpy as np with import cupy as np ).

Cupy replicates the numpy and scipy APIs but runs on the GPU.

For that, you can use cupy[0], PyTorch[1] or Tensorflow[2]. They all mimic the numpy's API with the possibility to use your GPU.

[0] https://cupy.dev/

Fast Array Manipulation in Python: Since Numpy is the de facto standard for storing multi-dimensional data, any performance gain you see using librapid math kernels will need to be realized on data which probably started its life as a numpy array, and needs to be passed to another tool as a numpy array. Hopefully there will be (or already is?) a way to build a librapid array out of a numpy array without copying the data and vice versa. In fact I might suggest that librapid focus on the fast math operations and simply become an accelerator for numpy arrays. For instance, look at CuPy which provides GPU-implemented operations within a numpy-compatible API, and Bottleneck which simply provides fast C-based implementations of some otherwise slow parts of Numpy. Also note that numpy *can* be multi-threaded depending on the operation and some environment variables. Single-threaded to Single-threaded I think you will be hard-pressed to beat Numpy on general math operations, but that doesn't mean there aren't specific "kernels" that are more specialized that can be greatly improved with a C++ back-end.