Hello all, I've got a question about optimizing a model for more efficient lookup-resources. Currently we expose an endpoint that frontend apps can use to list resources that a user has access to, which internally relies on lookup-resources. The problem is that we get high latencies (before any caching happens). Even just using

zed

(bypassing our endpoint logic), something like

zed permission lookup-resources project read user:2

takes about 10s (even if the user doesn't have access to any resource) which is not ideal when it's needed to load a web page. Here is a simplified version of our schema: https://play.authzed.com/s/o4iW-IKy0Il7/schema (I tried to keep only stuff related to the read:project permission, for this specific example, but could share the whole schema if it can help). We use intersections and synthetic relations heavily, not sure if those impact latencies. We are looking for general advice on how to improve/simplify our model, or any other advice on what could help reduce latencies of lookup-resources. Thanks!

Intersections require a post filtering check on our side

I see, thanks. Could you share some docs on how best to use the Watch API and how it would help, I couldn't find much online. Also regarding the long term vision, are you referring to something like this: https://github.com/authzed/spicedb/issues/207

yes, that's the analogue to the leopard cache that zanzibar uses for the same use case

The lookup resources watch API would be provided in that proposal

I see, so with the current capabilities of spicedb, what would be the recommended way of improving the latency of our use case? Is it just continuing to use the lookup-resources API and try to minimize intersections in our schema?

right now, even a single intersection (or exclusion) will requires results to be check'ed

Ah okay, got it, thanks. So basically, right now there's not much to be done to improve performance when trying to list all resources a user has access to.

no

Sounds good, thanks for confirming.

in the interim

I'll try that, thanks for the suggestion.