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

Lack of concurrency in ProxiedResource slows down fetching of metrics in large clusters #2764

Closed
dennisoelkers opened this issue Sep 1, 2016 · 1 comment
Assignees
Labels
Milestone

Comments

@dennisoelkers
Copy link
Member

@dennisoelkers dennisoelkers commented Sep 1, 2016

Expected Behavior

The number of total nodes should not influence the round trip times for ProxiedResource-based resources dramatically.

Current Behavior

As the ProxiedResource calls other nodes non-parallely and synchronously, having a larger number of nodes increases the round trip time for each request.

Possible Solution

Do calls in parallel.

@dennisoelkers dennisoelkers self-assigned this Sep 1, 2016
@jalogisch
Copy link
Contributor

@jalogisch jalogisch commented Sep 12, 2016

fixed in #2779

@jalogisch jalogisch closed this Sep 12, 2016
@joschi joschi added this to the 2.1.1 milestone Sep 12, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants