williamdclt05/25/2023, 9:56 AM
vroldanbet05/25/2023, 10:51 AM
, but it would be a different first 100 elements for
, leading to a disjoint set, forcing you to ask for the next 100 elements until you find the same elements (or you've reached the conclusion that is not in the set based on the order of elements). I think this use-case is better served by asynchronously loading all those UI elements after
and the power of HTTP2 pipelining. Whatever huge load you believe that its, it would still be more efficient than LookupResources in its current incarnation (even with cursors). If the permissions share common branches, those would be deduplicated by SpiceDB's hot spot caching. We've scaled SpiceDB to billions of tuples and a million requests per second, so I have difficulties to understand why this wouldn't scale merely based on checks.
williamdclt05/25/2023, 12:02 PM
vroldanbet05/25/2023, 12:09 PM
concurrently even if it's to collect them before going is still a good strategy worth exploring. Did you have the chance to test the cursored LR?
williamdclt05/25/2023, 12:17 PM
vroldanbet05/25/2023, 12:22 PM