Closed lastephey closed 1 year ago
Thanks to @beckernick this is now an internal NVIDIA bug. Will post updates if I hear anything.
Update: I did recently investigate JAX eigh as a possible alternative to CuPy eigh.
JAX appears to calculate eigh only using single precision, even when explicitly given an input of type float64
.
When CuPy and JAX eigh were both compared in single precision, the benchmark timings were nearly identical. @sbailey @dmargala @rcthomas
Daniel should point to his CuPy PR that implements batching to speed up eigh via batched calls to cusolver
Mark filed this issue:
https://github.com/cupy/cupy/issues/3154
but it was closed since the issue seems to be within cusparse rather than cupy.
Laurie will contact NVIDIA after GTC to find out where it should be re-opened.
Since eigh was the largest part of our runtime during the March 2020 hackathon it's worth checking to see if NVIDIA can make this function any faster.