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
In C/C++, NVTX ranges can be disabled, effectively eliminating any overhead of the nvtx function calls (albeit this overhead should already be small when a tool is not attached).
The Python NVTX ranges should have a similar feature that makes any annotation a no-op.
The text was updated successfully, but these errors were encountered:
I think this is still needed. Apart from overhead of nvtx, we usually do a "warmup" before actually profiling a deep learning model, and thus manually disabling nvtx in the warmup run is necessary.
In C/C++, NVTX ranges can be disabled, effectively eliminating any overhead of the nvtx function calls (albeit this overhead should already be small when a tool is not attached).
The Python NVTX ranges should have a similar feature that makes any annotation a no-op.
The text was updated successfully, but these errors were encountered: