Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: perf issue with too many API reqs when listing pods in all ns #10200

Merged
merged 2 commits into from
Nov 8, 2024

Conversation

stoksc
Copy link
Contributor

@stoksc stoksc commented Nov 8, 2024

Ticket

Description

Test Plan

Checklist

  • Changes have been manually QA'd
  • New features have been approved by the corresponding PM
  • User-facing API changes have the "User-facing API Change" label
  • Release notes have been added as a separate file under docs/release-notes/
    See Release Note for details.
  • Licenses have been included for new code which was copied and/or modified from any external code

Copy link

codecov bot commented Nov 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 53.03%. Comparing base (b8f56b6) to head (c74808a).

Additional details and impacted files
@@                Coverage Diff                 @@
##           release-0-35-1   #10200      +/-   ##
==================================================
- Coverage           57.60%   53.03%   -4.57%     
==================================================
  Files                 762      454     -308     
  Lines              104257    75774   -28483     
  Branches             3498     3499       +1     
==================================================
- Hits                60055    40190   -19865     
+ Misses              44056    35438    -8618     
  Partials              146      146              
Flag Coverage Δ
harness 66.75% <ø> (-2.92%) ⬇️
web 53.12% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 308 files with indirect coverage changes

@stoksc stoksc force-pushed the backport-k8s-perf branch from b179852 to 71adc45 Compare November 8, 2024 01:39
@stoksc stoksc marked this pull request as ready for review November 8, 2024 16:16
@stoksc stoksc requested review from a team as code owners November 8, 2024 16:16
@stoksc stoksc requested review from kkunapuli, hkang1, jgongd and molinamelendezj and removed request for a team November 8, 2024 16:16
@stoksc stoksc force-pushed the backport-k8s-perf branch from 71adc45 to fb8297c Compare November 8, 2024 16:17
ctx context.Context,
opts metaV1.ListOptions,
) ([]k8sV1.Pod, error) {
var g errgroup.Group
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a limit to the number of go funcs started at the same time? Or is it possible to wait on hundreds of go funcs?

Copy link
Contributor Author

@stoksc stoksc Nov 8, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

great question, no. i'd even added a g.SetLimit for this but the client they all use it already throttled so i decided i didn't care very much to limit it. this is already in fallback only code that is very unlikely to run.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That makes sense!

@stoksc stoksc requested a review from a team as a code owner November 8, 2024 20:17
change burst and qps

print

list jobs performance improvement

updates from brad
@stoksc stoksc force-pushed the backport-k8s-perf branch from fb8297c to c74808a Compare November 8, 2024 20:44
@stoksc stoksc merged commit 6e785cf into release-0-35-1 Nov 8, 2024
6 of 8 checks passed
@stoksc stoksc deleted the backport-k8s-perf branch November 8, 2024 20:55
@stoksc stoksc restored the backport-k8s-perf branch November 8, 2024 21:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants