RFC: RTC kernel cache file behaviour about rocfft HOT 2 CLOSED

From a toolkit user's perspective: as long as the changes don’t adversely affect my existing code/workflow or require me to do a lot of updating / new steps, I don’t have a strong opinion. Faster caching is beneficial, but only if the default setting is "runs anywhere".

Ideally, this means the solution would:

• Robust defaults, even If not the most performant
• Straight-forward method to tune for more performance (environment variables are good, as long as they are documented well)
• Maintains compatibility with existing rocFFT implementations, if possible.

From that perspective, a new/separate function to set the runtime policy for this variable shouldn’t affect existing routines. If you're considering an environment variable as well, how about the ability to set the runtime policy with either an environment variable or through a new function?

from rocfft.

We have received feedback and will make an internal decision on caching.

from rocfft.