@Joey thanks for your response. indeed eviction don't seem to be the problem. i noticed that each request that I fired into spicedb would trigger a new revision to be computed, despite being fired within the quantization period (120s in our case). these revisions would not be quantized, resulting in cache misses. i checked the code and that seems to happen when there hasn't been a transaction within the current quantization period. i inserted a transaction into pg by hand and now my sub-computations get retrieved from the cache. our loadtesting setup ran into this issue because we exclusively test checks (reads) in them. according to the comment here, if there hasn't been a transaction within the current quantization period, the latest transaction is supposed to be selected (https://github.com/authzed/spicedb/blob/20d90b6d2c4ddf8ca7c92acd0602efc9afbe044b/internal/datastore/postgres/revisions.go#L26-L45). but this doesn't correspond to the WHERE clause in the first CTE. instead, the current snapshot is returned and used as the revision. is this intended?