argo-cd: ArgoCD very slow on inial load after upgrade to 2.3.3 from 2.2.5

Describe the bug

After the upgrade from 2.2.5 to 2.3.3 the ArgoCD webinterface takes a very long time to load. We have two ArgoCD instances with a small amount of apps (~50 per instance) and both exhibit this behavior. When looking at the network traffic in a developer console the main problem seems to be main.c7ea22e999b3805bc676.js.

I could reproduce the problem on Chrome and Firefox.

None of the pods running ArgoCD show signs of resource starvation.

Screenshots

image

Version

We deploy ArgoCD using the ArgoCD Operator on OKD 4.9. The ArgoCD 2.3.3 Update was triggered by the Operator Update to version 0.3.0.

argocd: v2.3.3+07ac038
  BuildDate: 2022-03-30T00:06:18Z
  GitCommit: 07ac038a8f97a93b401e824550f0505400a8c84e
  GitTreeState: clean
  GoVersion: go1.17.6
  Compiler: gc
  Platform: linux/amd64

About this issue

  • Original URL
  • State: open
  • Created 2 years ago
  • Reactions: 8
  • Comments: 21

Most upvoted comments

This was mostly fixed for me by turning on gzip compression (not sure why it wasn’t on by default): https://github.com/argoproj/argo-cd/discussions/10238#discussioncomment-3942411

It can still take 6-9 seconds or so to initially load the page but much better than a minute.

@crenshaw-dev I would be happy to help but this issue randomly disappeared in our instances. API Timings across all involved clusters did not change during that time. Networking in all other deployed components was healthy meanwhile. Sorry 😦

Appears to be main.js for myself as well, can try to look into logs…

2022-06-21_15-18-02