Hi @davoustp , Yes able to connect with JMX port, Able to notice that realm cache size got update from default 10K to 100K. Thanks for your reply.

By updating the realm cache size to 100K for v16 & v17 legacy we were able to reach 1500realm creation, in which the realm creation time gradually increased. On applying same config the quarkus is able to create only 1100 realms. Do we need to tweak any quarkus configs like core-thread-pool or anything else?

By updating the realm cache size to 100K for v16 & v17 legacy we were able to reach 1500realm creation, in which the realm creation time gradually increased.

Yes, that's what #11074 is all about.

On applying same config the quarkus is able to create only 1100 realms.
I did not test Wildfly-based Keycloak (legacy), only the Quarkus-based one.

But you are very patient to reach 1100 realms - I stopped at ~600 realms (but did not increase the cache size while doing so, that's true). :-)

Do we need to tweak any quarkus configs like core-thread-pool or anything else?

I did not change anything else on Quarkus config in my investigation.
But I did change the code, so I don't think it can compare to stock Keycloak...

Thanks for your reply @davoustp

can you share you infinispan xml file @sreekesh93 ?
i'm trying to access infinispan MBeans in KC 18 with no sucess.
I have enabled statistics in the cache-container and in the caches themselves but it doesn't seem to work.

<cache-container name="keycloak" statistics="true">
    <local-cache name="realms" statistics="true">
(...)

can you share you infinispan xml file @sreekesh93 ? i'm trying to access infinispan MBeans in KC 18 with no sucess. I have enabled statistics in the cache-container and in the caches themselves but it doesn't seem to work.

<cache-container name="keycloak" statistics="true">
    <local-cache name="realms" statistics="true">
(...)

it seems i was missing something like this:

<cache-container name="keycloak" statistics="true">
    <jmx enabled="true" domain="infinispan"/>