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.

Sign up for GitHub

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

Jump to bottom

Simplify/consolidate thread utilization by informers #3072

Closed
shawkins opened this issue Apr 30, 2021 · 2 comments
Closed

Simplify/consolidate thread utilization by informers #3072

shawkins opened this issue Apr 30, 2021 · 2 comments
Assignees
@shawkins
Milestone
5.5.0

Comments

@shawkins
Copy link
Contributor

shawkins commented Apr 30, 2021 •
edited
Loading

With the current implementation each informer directly consumes a thread for:

  1. Controller - resync executor thread pool
  2. DefaultSharedIndexInformer - controller thread
  3. SharedProcessor - executor, which is 1 thread per listener.

This becomes an issue when running lots of informers.

We should be able to consolidate or remove several of these. #3061 for example allows the controller thread to complete.

Additionally each watch has a websocket reader thread and a scheduler thread.
@shawkins shawkins mentioned this issue May 2, 2021
Closed
11 tasks
@manusa
Copy link
Member

manusa commented May 5, 2021

Relates to: #2010

@shawkins shawkins mentioned this issue May 12, 2021
Merged
11 tasks
@manusa
Copy link
Member

manusa commented May 24, 2021 •
edited
Loading

Should be fixed (addressed) in #3108

@manusa manusa closed this as completed May 24, 2021
@manusa manusa added this to the 5.5.0 milestone May 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shawkins shawkins

Labels
None yet
Projects
None yet
Milestone
5.5.0
Development

No branches or pull requests
2 participants
@manusa @shawkins