SpiceDB is an open source, Google Zanzibar-inspired, database system for creating and managing security-critical application permissions.

SpiceDB

We have some clients who don't deal well with max stale perc > 0 due to non-monotonic reads (particularly w/ minimize latency). We currently have that at 100%, and are considering turning it to 0% to remove the issue. I'm just curious if folks have a sense of / measured the real impact of max staleness on production latencies – is it significant?

Can you elaborate? It reads as if they are "ok with 5 of staleness, but not 10"

Tolerance to staleness is largely dependent on your application. It's fair to say that "one single staleness threshold for all clients of SpiceDB" is too restrictive, and we have certainly discussed the possibility of adding a new consistency option that lets the client specify how much staleness they are willing to accept.