The rule memoization in the engine, how are the ch...
# development
c
The rule memoization in the engine, how are the characteristics for long running processes? 🧵
Are the rule results ever evicted, for instance?
I’m considering my
underpants
poc, and if used in a long running application, the rule inputs may very well differ frequently, and as such the memoization isn’t really buying us much in that case.
I guess going with the
_uncacheable
decorator, the memoization seems to be dropped between sessions, so that’s good enough perhaps, iiuc.
w
if you mark a process
ProcessCacheScope.PER_SESSION
, you don’t need the decorator
c
not all rules are processes..
👍 1
w
got it. types can also be marked
cacheable = False
via the
EngineAwareReturnType
class
c
Ah, right, I think maybe I may have mislead you with “long running processes” above.. think of that process as the “pantsd” process
w
yep
c
Oh, cool, will look into the EART thing..
so, is there any sort of limit or gc running for the memoized data?
w
c
Ah, ok. Thanks for the issue, will monitor that 🙂