Open CirillaQL opened 4 months ago
@CirillaQL Thanks for feedback, what you said looks like a performance problem. Usually, the first execution of the audit api
will scan all resources in the set cluster. The calculation result will record in the cache, but this will cause the first time to open the page too slowly when there are more resources, which is indeed a problem.
I think I can optimize performance at this point:
Do you have any ideas?
What happened?
I tried to check information about my cluster in Cluster Management, but the audit, score, and topology responses timed out.
What did you expect to happen?
apis response successfully
How can we reproduce it (as minimally and precisely as possible)?
import a large Kubernetes cluster and enter into cluster management.
Anything else we need to know?
I use Postman to get api, topology api use 43.5s and audit api use 38.5s, maybe find some ways to fix this performance issue. And this is my cluster size:
Karpor version
OS version
Install tools