Skip to content

Conversation

@shuangkun
Copy link
Member

Optimize pagination when counting workflows in archive

Fixes #13948

Motivation

When the database has more than 1 million workflows, this query statement becomes a bottleneck, and the UI becomes inaccessible, impacting workflow query and observation.

After optimization, testing in a production environment with 5 million records, the UI can be opened normally.

Modifications

Verification

Documentation

@shuangkun shuangkun changed the title feat: optimize pagination when counting workflows in archive. Fixes:#13948 feat(server): optimize pagination when counting workflows in archive. Fixes:#13948 Sep 28, 2025
Signed-off-by: shuangkun <[email protected]>
Signed-off-by: shuangkun <[email protected]>
Signed-off-by: shuangkun <[email protected]>
Signed-off-by: shuangkun <[email protected]>
@Joibel
Copy link
Member

Joibel commented Oct 17, 2025

Thanks for this, looks great.

@Joibel Joibel merged commit 179571e into argoproj:main Oct 17, 2025
37 checks passed
ItielOlenick pushed a commit to ItielOlenick/argo-workflows that referenced this pull request Oct 26, 2025
guanguxiansheng pushed a commit to guanguxiansheng/argo-workflows that referenced this pull request Dec 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

/api/v1/workflows/ has slow response time when, there are many archived workflows in 3.6.0

3 participants