You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OS : Linux-6.5.0-1023-oem-x86_64-with-glibc2.35
Python Version : 3.10.14
CuPy Version : 13.1.0
CuPy Platform : NVIDIA CUDA
NumPy Version : 1.26.4
SciPy Version : None
Cython Build Version : 0.29.37
Cython Runtime Version : None
CUDA Root : /usr/local/cuda
nvcc PATH : /usr/local/cuda/bin/nvcc
CUDA Build Version : 12040
CUDA Driver Version : 12040
CUDA Runtime Version : 12040 (linked to CuPy) / 12040 (locally installed)
cuBLAS Version : (available)
cuFFT Version : 11201
cuRAND Version : 10305
cuSOLVER Version : (11, 6, 1)
cuSPARSE Version : (available)
NVRTC Version : (12, 4)
Thrust Version : 200302
CUB Build Version : 200200
Jitify Build Version : <unknown>
cuDNN Build Version : 8907
cuDNN Version : 8907
NCCL Build Version : 22105
NCCL Runtime Version : 22105
cuTENSOR Version : 20001
cuSPARSELt Build Version : None
Device 0 Name : NVIDIA RTX A500 Laptop GPU
Device 0 Compute Capability : 86
Device 0 PCI Bus ID : 0000:03:00.0
Additional Information
No response
The text was updated successfully, but these errors were encountered:
Thanks for the feedback @essoca, confirmed on my side as well. Support for axis argument in cupy.unique is relatively new (#6886 cc/ @andfoy) and looks like there is room for improvement, especially in the case that the length of the axis specified in the ndarray is large.
Description
In an attempt to measure the performance of
cp.unique
(following #8307), I noticed something very unpleasant: it doesn't return for large arrays.I expect something comparable to Jax numbers:
To Reproduce
First small arrays
Bigger array, but benchmarking any other function (e.g.
cp.sum
) to check that it returns:A single run with this size of
cp.unique
keeps running (after an hour, it was still running).Installation
Conda-Forge (
conda install ...
)Environment
Additional Information
No response
The text was updated successfully, but these errors were encountered: