Open LilithHafner opened 1 year ago
The issue is that Cassette by definition uses a completely split inference cache. It injects the context definition as the first argument into all calls therefore requiring a new cache.
You could precompile some common codes with your context, but fundamentally there is no way around this.
I'd like to use Cassette as a backend for a developer-facing tool to log various events during program execution. However, I'm experiencing a 1–2 minute TTFX with Cassette. The tool I'm making should work for arbitrary user code so I don't have access to it at precompile time. Is there any way to use Cassette as a backend without exposing users to this TTFX for every additional code that they wold like to track?
For reference, my existing hack is to redefine the methods I want to track (
getindex
,setindex!
, etc.) which causes about 10 seconds worth of invalidations.This is the FFTX analogue to #91