We use one session per request, but that may be specific to our scenario, where each request represented a wholly unique patient.

@defndaines thanks! any chance you’ve used the explain activations function in the tooling? i’m curious what the best way is to use that if each session is spun up and down for a request

We have a hook to turn on explain-activations, but we rarely use it. We accumulate data in each of our facts that helps with all of our debugging. We also capture all of the input to the sessions, so we can reproduce a session for debugging in order to analyze.

thank you! that’s super helpful

So a session is immutable.

I would necessarily recommend making a new session when speed is important or it is slower due to many rules

With smaller rule sets maybe ok

But typically, I’d store the initial session made via mk-session and then just do new isolated insert+fire callls on it “per unrelated invocation”

This is also assuming the rule set is unchanged per use.

thank you! much appreciated.