FThat is defenitly too slow, not sure why though.
What version do you run and what CPU/memory do you assign to zitadel and the DB?
What version do you run and what CPU/memory do you assign to zitadel and the DB?
FTo me it looks like a CPU constraint issue, since password hashing might take some time here.
Fin the defauls yaml you can find the configuration for the passwordHasher
Fhave you checked the query analyzer in the cockroachDB, maybe something takes too long to process.
Fthough we have not seen many such cases I would start looking into that
FCockroachDB has a UI for that
FThat only reduces the strain on zitadel not on the DB
FI guess you should start sharing some metrics you see
Like CPU/Memory usage and then investigage in the DB for slow queries
Like CPU/Memory usage and then investigage in the DB for slow queries
FWhy is you CRDB so high in CPU?
What does zitadel do?
What does zitadel do?
FYou should really check the CockroachDB UI for expensive queries
FHm that current state is certainly an issue.
I wonder why that is so slow though.
I wonder why that is so slow though.
FContention 900ms is kind of the issue there, question is why there is congestion.
That usually mean that the same thing is being called many times in parallel.
That usually mean that the same thing is being called many times in parallel.
FYou can try to catch a debug log in CRDB there, that might help us understand why this breaks.
Fwell that does not look to healthy 
Fis that a CRDB cluster?
Fyou know that CRDB is not designed for a two server setup?
Fat least 3
Fbut maybe you should look into postgres as alternative
F