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
Currently the cache in MatX is stored in a static variable that has no way for the user to control it. Items are added transparently to the cache as needed, and they are never removed until the application exits. This can cause problems for applications that grow and use the cache more than smaller applications. At a minimum the user should be able to delete the cache of a specific operation, a specific operator, or the entire cache.
Something like the following would be suitable, but the syntax is only for an example:
delete_cache(a = matmul(e,f) * fft(b)) or delete_cache(fft(b))
delete_cache(FFT1D_OP); // Deletes all 1D FFT cache
delete_cache(); // delete entire cache
In the first example multiple caches may be deleted if multiple functions are embedded in a single operation, whereas the second part only disables the one FFT operation.
The text was updated successfully, but these errors were encountered:
Currently the cache in MatX is stored in a static variable that has no way for the user to control it. Items are added transparently to the cache as needed, and they are never removed until the application exits. This can cause problems for applications that grow and use the cache more than smaller applications. At a minimum the user should be able to delete the cache of a specific operation, a specific operator, or the entire cache.
Something like the following would be suitable, but the syntax is only for an example:
delete_cache(a = matmul(e,f) * fft(b))
ordelete_cache(fft(b))
In the first example multiple caches may be deleted if multiple functions are embedded in a single operation, whereas the second part only disables the one FFT operation.
The text was updated successfully, but these errors were encountered: