Florian Forster

Since https://github.com/zitadel/zitadel/issues/4450 fixed I think we can close this issue. Feel free to reopen if we need to look into it again.

@hifabienne I think this is a starting point for the customer inquire we have. @adlerhurst @livio-a what do you think of these ideas @eliobischof @thesephirot I think you two would...

> From a zitadel perspective it could get interesting to define the test parameters like amount of amount of instances, orgs, users, user types, projects Makes sense I will quickly...

Locust looks fine to me as well 😝

@adlerhurst I agree the 1200/s acts only as starting point to test the system under sustained load. I think testing for 10000 logins per second is important as well.

> there might be some challenges with k6, currently testing the memory > > https://k6.io/docs/examples/data-parameterization/ > > "...For example, the Cloud service allocates 8GB of memory for every 300 VUs....

Ok, so in regard to discovery. You would be fine of doing discovery on the "username" and route the user towards an organisation based on that mechanic? In my mind...

Ok, so I think in here are two action items then: - Our "Domains" feature should be allowed to use as discovery feature based on the domainname - After the...

@zitadel/engineers opinions for this?

I think the current change should allow for the resource owner metadata to be returned.