The cuda_bindings Cython code has been built with the profile directive on since the project's inception, and that continues to be true today. Is that intentional? This build setting probably adds measurable overhead to some of the bindings functionality at runtime that is not desirable by default given that cuda-bindings is generally fairly performance-sensitive. Moreover, it exposes published packages to a greater potential surface area for Cython bugs. In particular, it means that cuda-bindings packages are currently susceptible to issues like cython/cython#7050. I would suggest that we turn this off by default and developers can turn it on as needed.
The
cuda_bindingsCython code has been built with the profile directive on since the project's inception, and that continues to be true today. Is that intentional? This build setting probably adds measurable overhead to some of the bindings functionality at runtime that is not desirable by default given that cuda-bindings is generally fairly performance-sensitive. Moreover, it exposes published packages to a greater potential surface area for Cython bugs. In particular, it means that cuda-bindings packages are currently susceptible to issues like cython/cython#7050. I would suggest that we turn this off by default and developers can turn it on as needed.