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

probably makes sense to get tracing to work first, then you can check out why performance is worse?

<@U010F2N7G2X> A quick stat about SQL queries. This shows the number of queries finished within a given time

<@U010F2N7G2X> <@U010UKXCPP0> I've made further comparison of master and sql-next branch but just turned off tracing in registry_sql.go instead of reverting that patch. The numbers in the filename represents the max pool and max idle pool.
It seems that
• sql-next branch is slower if pool setting is lower (maybe because this branch uses transaction which "locks" a connection for longer time)
• after increased the pool/idlepool then overall auth/s seems equal with the master branch
• with increased connection pool parameters still response time of some of the hydra queries are higher: the initial /oauth2/auth, the /oath2/auth call after login provider, and get login session and accept consents in the consent provider