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

High CPU utilization on ssh_service start-up #1886

Closed
kontsevoy opened this issue Apr 18, 2018 · 0 comments · Fixed by #1932
Closed

High CPU utilization on ssh_service start-up #1886

kontsevoy opened this issue Apr 18, 2018 · 0 comments · Fixed by #1932
Assignees
Labels

Comments

@kontsevoy
Copy link
Contributor

Problem

I have a Raspberry Pi which runs ssh_service only, i.e. no auth/proxy. The latest builds of Teleport eat 100% of one CPU core for a few minutes on startup. This actually causes extremely long deployment cycles leading Ansible timing out sometimes.

... not to mention that eating a 100% of CPU, even if temporarily, is not nice :)

Investigation

@russjones believes this is related to the recording proxy.

Validating the fix

Ping @kontsevoy to validate the fix, I have a couple of Pis + deployment pipeline to push a new binary.

@kontsevoy kontsevoy added the bug label Apr 18, 2018
@kontsevoy kontsevoy added this to the 2.6.0 "Austin" milestone Apr 18, 2018
@kontsevoy kontsevoy added the P1 label Apr 24, 2018
klizhentas added a commit that referenced this issue May 4, 2018
This commit fixes #1886

Previously the code was precomputing keys
even for SSH nodes, that do not need precomputed
private keys pool.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants