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

CPU spikes #20

Closed
pascalandy opened this issue Dec 6, 2018 · 8 comments
Closed

CPU spikes #20

pascalandy opened this issue Dec 6, 2018 · 8 comments

Comments

@pascalandy
Copy link

pascalandy commented Dec 6, 2018

I can observe CPU spikes (it's the container that uses the most CPU over 70 services/containers). I'll experiment with CPU limits and report :_p

screen shot 2018-12-06 at 12 17 11 pm

@djmaze
Copy link
Collaborator

djmaze commented Jan 2, 2019

Would be interesting to know what happens there.

@stale
Copy link

stale bot commented Jul 22, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jul 22, 2019
@pascalandy
Copy link
Author

It was not addressed but it is still an issue IMHO.

@stale stale bot removed the wontfix label Jul 22, 2019
@djmaze
Copy link
Collaborator

djmaze commented Jul 22, 2019

@pascalandy Can you exec into the container when this happens? Or get some docker top output?

@pascalandy
Copy link
Author

I can but what are you looking for?

user@vps2:~/workdir# docker top tool-shepherd.1.1f5tigggh7zw9rjqhnp8ut52p
UID                 PID                 PPID                C                   STIME               TTY                 TIME                CMD
root                18647               25831               0                   22:02               ?                   00:00:00            sleep 1m
root                25831               25797               0                   21:53               ?                   00:00:00            /bin/bash /usr/local/bin/shepherd

@djmaze
Copy link
Collaborator

djmaze commented Jul 24, 2019

Well, if it is the shepherd container which is using the CPU, it would be interesting to see if it is the shepherd script itself or the docker client. I can't really make a picture of this currently.

@pascalandy
Copy link
Author

I saw this using prometheus and Graphana. Other containers were running normally.
I now use --cpu-limit to mitigate this.

So let's close this if you prefer.

@djmaze
Copy link
Collaborator

djmaze commented Jul 25, 2019

Yes, let's close this for now. Feel free to reopen if you get to the cause.

@djmaze djmaze closed this as completed Jul 25, 2019
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

No branches or pull requests

2 participants