Michał Wójcik
10/21/2025, 11:48 AM/check, /bulk_check, /user-permissions, and /authorized-users.
I’d like to ask if you have conducted any internal performance or scalability tests for the PDP and related APIs — and if so, could you share any benchmark results or performance assumptions (e.g., expected throughput, latency, or concurrency levels)?
I understand that the actual performance depends heavily on where the PDP is hosted (cloud vs. on-prem, region, hardware specs), but any reference numbers or best practices would be very helpful for setting up my own test plan.Ask Inkeep
10/21/2025, 11:48 AMAsk Inkeep
10/21/2025, 11:48 AM--env PDP_DEBUG=False
• Optimize base policy for your specific use case (disabling unused features like ReBAC checks can speed up execution)
Caching Configuration
The PDP includes a configurable caching mechanism that significantly improves performance by reducing redundant policy evaluations (3) . The cache supports:
• /allowed
• /allowed/bulk
• /user-permissions
• /authorized_users
You can configure the cache to use either in-memory storage for single instances or Redis for distributed caching across multiple PDP instances .
Scaling Strategies
For horizontal scaling (2) :
• Deploy multiple PDP instances behind a load balancer when CPU becomes a bottleneck
• For multi-tenant environments, use tenant-based sharding for data/memory scalingAsk Inkeep
10/21/2025, 11:49 AMOmer Zuarets
10/21/2025, 11:55 AM/user-permissions on a user with 1 permission and on a user with 10k permissions via a heavily deep or wide relationship graph will have completely different results. The same example goes for all the queries you mentioned.
If you encounter any performance issues during your performance & load tests, we’d be happy to help you configure your setup/policy for the best performance.
Notice that the PDP is highly dependent on CPU but also on Memory depending on the data volume