Hi folks. Investigating performance issue now with Hydra. We are doing 100 rps of code grant flows and what we see is that after the consent service PUTs an accept login to Hydra and before Hydra does the next step and make a call to GET /consent get it's about 300 to 500ms of wait. What can be the reasons for such a long wait time and how it is possible to improve? Please see screenshot

Are you sure you're reading the trace correctly? I don't think hydra is doing any waiting there. Rather, there seems to be a gap in your instrumentation.

Hi Arne. Tnx for fast reply. We have a consent service that makes PUT to accept login request. As far as i aware for code grant flow the next step is hydra should do a call to /consent endpoint. As you see on the screenshot the time beetwin we do PUT accept login and the time when we actually receive consent get is about 500 ms. There is nothing else happening in beetwin

Hydra does no calls to a /consent endpoint. Your consent app/screen makes calls to /oauth2/auth/requests/{login,consent}/accept. Each time, hydra answers within 15ms.

but after we accept login request, we are receiving call from hydra on the /consent get. It's the call Hydra is initiating, not consent itself

That's not hydra making a request but a web browser.

Ory OAuth2 and OpenID Connect redirects the end user's browser to the "Consent Endpoint" established in your config:

Hydra does not perform this redirect. It instructs the consent app to redirect the user agent (browser) to the next step. The point is that the

GET /consent

request is not performed by hydra, but by the user agent (browser). The gap marked in your trace is the consent app doing something (probably responding to the user agent and sending it to

/consent

). Hydra is not doing anything there.

but here as we can see on the request diagram i clearly see redirects that are happening beetwin client (browser) (on the very left) and hydra