Benchmark of zitadel v2.66.0 - more details on your testing setup is needed
We have looked into your zitadel v2.66.0 benchmarking results provided at https://zitadel.com/docs/apis/benchmarks/v2.66.0/machine_jwt_profile_grant
In our setup we are getting significantly worse performance and it looks like the postgresql db cluster can be a bottleneck.
We are looking to make our postgresql db config similar to yours, but are lacking some details.
1. In yours "Database specification" it is specified "vCPU: 8 memory: 32Gib". Is it per 1 db cluster node, or an overall summed resources per all nodes?
2. How many write/read replicas are in your postgresql db cluster? Are you distributing zitadel sql queries between write/read somehow? (as zitadel doesn't support that, maybe some middleware query routing/loadbalancing solution is used?)
3. Are you planning to implement zitadel application level query routing to distribute the query load between all db cluster replicas, and not only utilize master/write node?
In our setup we are getting significantly worse performance and it looks like the postgresql db cluster can be a bottleneck.
We are looking to make our postgresql db config similar to yours, but are lacking some details.
1. In yours "Database specification" it is specified "vCPU: 8 memory: 32Gib". Is it per 1 db cluster node, or an overall summed resources per all nodes?
2. How many write/read replicas are in your postgresql db cluster? Are you distributing zitadel sql queries between write/read somehow? (as zitadel doesn't support that, maybe some middleware query routing/loadbalancing solution is used?)
3. Are you planning to implement zitadel application level query routing to distribute the query load between all db cluster replicas, and not only utilize master/write node?
