Hi,
Whenever i am creating the cuSolver handle (debug mode), this process alone has a latency around 5-10 sec. In release mode, it’s fine (no latency). Do you know the source of this problem?
Thanks
Abdoulaye
Hi,
Whenever i am creating the cuSolver handle (debug mode), this process alone has a latency around 5-10 sec. In release mode, it’s fine (no latency). Do you know the source of this problem?
Thanks
Abdoulaye
The library itself is the same whether compiling in debug or release mode. A short example that demonstrates the issue, along with a description of the environment might be needed.
Hi @Robert_Crovella ,
I am using Visual Studio 2022 and whenever the process is stepping through this function (by using breakpoint on Debug mode), it took around 7 sec. So i don’t think that it needs an elaborated example. Yet, the other CuSolverDn functions are flawlessly working.
Thanks
Abdoulaye
I don’t see any significant difference:
$ cat t2251.cu
#include <iostream>
#include <cusolverDn.h>
#include <time.h>
#include <sys/time.h>
#define USECPSEC 1000000ULL
unsigned long long dtime_usec(unsigned long long start=0){
timeval tv;
gettimeofday(&tv, 0);
return ((tv.tv_sec*USECPSEC)+tv.tv_usec)-start;
}
int main(){
unsigned long long dt = dtime_usec(0);
cusolverDnHandle_t h;
cusolverDnCreate(&h);
dt = dtime_usec(dt);
std::cout << "time: " << dt << " microseconds" << std::endl;
}
$ nvcc -o t2251 t2251.cu -lcusolver
$ ./t2251
time: 898633 microseconds
$ nvcc -o t2251 t2251.cu -lcusolver -g -G
$ ./t2251
time: 891301 microseconds
$
It may be some artifact of VS or of host code debugging on windows.
Good luck!