Hi there :wave: Sometimes on hydra we experience ...
# talk-hydra
m
Hi there 👋 Sometimes on hydra we experience high latency due to unknown reason. It seems that there is a large noop after executing sql queries. This only happens on the
oauth2/token
endpoint. See the trace in attachment. Did you already experience this type of issue? Thx.
screenshot
m
Hm nothing comes to mind to be honest, I just found this two year old report: https://ory-community.slack.com/archives/C012RBW0F18/p1599667093104900
If you keep running into the issue, could you please open a discussion on GitHub (or bug report if its probably caused by Hydra not something else) ? Sometimes things move too fast here and not every Hydra user is on Slack.
f
We see a slightly different trace in our environment. During the POST operation to
oauth2/token
there is a call to the
bcrypt
library which deliberately has an execution lag, defined by the
bcrypt.workfactor
parameter (10 in our case). In our case the total call length is significantly shorter than yours though.
g
In most cases our execution is time is also much shorter. But every few minutes, one call to
/oauth2/token
takes far longer, which the trace Nicolas shared above. I imagine that it would be the same problem, we would see a large space in the traces at the beginning of the SQL statements. But our traces seem to indicate that after the SQL calls something is happening 🤔 Could it be related to some network latencies maybe?