[Bug] The dubbo-admin service uses nacos as the registration center. Due to frequent GC issues, it starts slowly or fails to start.

[wcwssf]

Pre-check

• I am sure that all the content I provide is in English.

Search before asking

• I had searched in the issues and found no similar issues.

Apache Dubbo Component

Java SDK (apache/dubbo)

Dubbo Version

Dubbo: 3.2.16 JDK: 1.8 Server: Ubuntu 9.4.0-1ubuntu1~20.04.2

Steps to reproduce this issue

When dubbo-admin uses nacos as the registration center, the registration center notifySubscriber process is very slow and consumes a lot of memory. Because of all the service info will be related to every single service , so that every single service changed , the Subscriber will process all the service, and cache file store the all related service info.
Step1: use nacos as the registration center,
Strp2: Need have above 2000+ service

What you expected to happen

We hope that when using nacos as the registration center, dubbo-admin startup is the same as other registration centers, and service information mapping is accurate

Anything else

No response

Are you willing to submit a pull request to fix on your own?

• Yes I am willing to submit a pull request on my own!

Code of Conduct

• I agree to follow this project's Code of Conduct