KusionStack / KusionStack/karpor

Performance Issue: Cluster Management audit/score/topology api response timeout

Open
#569 1 comment 0 reactions 0 assignees View on GitHub
area/insight area/performance
Dominant language
Go
Stars
1.7k
Forks
113
PR merge metrics
No merged PRs in 30d

Description

### What happened?

I tried to check information about my cluster in Cluster Management, but the audit, score, and topology responses timed out.
![微信截图_20240801144709](https://github.com/user-attachments/assets/93caac83-ad68-46e3-9ca2-746a8450fcbc)
![微信截图_20240801144721](https://github.com/user-attachments/assets/f74a9482-02f0-4d26-b4e3-665a7b497663)

### 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.
![微信截图_20240801145638](https://github.com/user-attachments/assets/92b60595-3f63-4159-ad20-92a5c8fb52ba)
![微信截图_20240801145924](https://github.com/user-attachments/assets/1e51460e-2758-4c13-ba5d-88755af4a7e3)
And this is my cluster size:
![微信截图_20240801145948](https://github.com/user-attachments/assets/70d35502-460a-4643-92c9-c93ab0640091)

### Karpor version

v0.4.4

```console
$ karpor -V
# paste output here
```

### OS version

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here
alpine Docker

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

### Install tools

Helm Chart

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the timeout in Cluster Management on a large Kubernetes cluster, then compare the topology, audit, and score API timings with Postman. Done means these APIs return successfully within an acceptable response time for large clusters; the issue does not name source files or tests to inspect.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
backend-api-design, cloud, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.