Argo-cd: /api/v1/applications takes significant amount of time

[cedricboesiger]

Describe the bug
The application list page uses GET /api/v1/applications?fields=... which, depending on the number of projects holding OIDC groups, requires more time to answer the request.
In our environment, it already takes between 12s-14s to answer the request.

We count:

• Between 50 to 70 OIDC groups per user
• 25 Appprojects each with 2 roles with up to 10 policies that are assigned to 1 oidc group.
• 215 Applications
• We use v1.5.6 in production

To Reproduce

• Create an empty ArgoCD installation, v1.7.4
• Create a couple 100 Appprojects, each with 2 roles that are assigned to an OIDC group
• Create a couple 100 Applications assigned to the Appprojects
• Use an OpenID User to login
• Check that the response time from /api/v1/applications in the browser console increases with the number of projects with assigned groups.

Expected behavior

A response time that is less dependent on the number of applications, projects and groups involved.

[alexmojo]

Same issue, we are using v1.7.4

[alexmojo]

Also, I've notice, that if login using built-in account to the same api server response more quickly.

[alexmojo]

We have about 800+ applications in 2 clusters.
My results with SSO login and RBAC:

Using built-in administrator account:

[jessesuen]

NOTE: The admin is special because it has no groups and therefore enforcement is simpler.

Between 50 to 70 OIDC groups per user

I think we need an optimization to use a temporary map to lookup oidc groups rather than current implementation to iterate the groups list

[boskoop]

Great news if this is solved with 1.8!

[kshamajain99]

Looking into this.