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
The recent switch to lazy loading by default in CTK 12.2 seems to have broken the async benchmarks. This can be reproduced by nvbench.example.axes. The deadlock can be fixed by CUDA_MODULE_LOADING=EAGER. We should incorporate this information into the error message or set the variable ourselves.
The text was updated successfully, but these errors were encountered:
We likely want eager loads by default anyway to make sure that lazy loads aren't affecting measurements. Let's look into defining that var from the NVBench main implementation.
* Set `CUDA_MODULE_LOADING=EAGER` before `main`.
Fixes#136
* Portability for `setenv`.
* Remove pre-main CUDART usage and setup env in main.
* Fail examples if they deadlock.
This is the best way we have to diagnose a regression for
#136.
* Add an initialize method to benchmark_manager for CUDA-related setup.
Benchmarks are created statically, so their constructors cannot call the CUDA APIs without breaking the CUDA_MODULE_LOAD setup.
This method is called from `main` after the environment has been configured.
The recent switch to lazy loading by default in CTK 12.2 seems to have broken the async benchmarks. This can be reproduced by
nvbench.example.axes
. The deadlock can be fixed byCUDA_MODULE_LOADING=EAGER
. We should incorporate this information into the error message or set the variable ourselves.The text was updated successfully, but these errors were encountered: