Ory is the largest open source community in the world for cloud software application security. We maintain advanced open source security software solving authentication, authorization, access control, application network security, and delegation. Ory implements a variety of industry and best-practice standards including OAuth 2.0 / OAuth 2.1, OpenID Connect, Zero Trust Networking, Google Zanzibar Policy Framework, FIDO2 U2F, WebAuthn, TOTP, and more.

Ory Community

Hello everyone, we are experiencing our first intense production workload on hydra v1.7.4 and we tried 2 configurations (AWS ECS environment):
1. 1vCPU, 2GB, 20 instances with horizontal scaling
2. 2vCPU, 4GB, 10 instances with horizontal scaling
It seems like the second configuration is not making good use of the second vCPU, as you can see from the chart (CpuUtilized is always under 1 vCPU). Is there any reason for this behavior? Shouldn't Go take as default the number of available CPUs to size its thread pool? Are there any performance metrics we can watch on the running service?

This is an aggregate of request paths in the last hour