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 is too high #1688

Closed
socol1 opened this issue Aug 31, 2016 · 8 comments
Closed

CPU is too high #1688

socol1 opened this issue Aug 31, 2016 · 8 comments

Comments

@socol1
Copy link

socol1 commented Aug 31, 2016

image
What can I do ?

@phemmer
Copy link
Contributor

phemmer commented Aug 31, 2016

Can you provide the telegraf version, what OS you're using, and your config?

Also if you can send telegraf a SIGQUIT (note this will cause telegraf to exit), and provide the output it dumps (it'll be on the application's STDERR, wherever you have that going), we can see what it was doing.

@socol1
Copy link
Author

socol1 commented Sep 1, 2016

@phemmer
Telegraf - version 0.13.1
os - Red Hat Enterprise Linux Server release 6.5 (Santiago)
uname -a Linux 2.6.32-431.el6.x86_64 #1 SMP Sun Nov 10 22:19:54 EST 2013 x86_64 x86_64 x86_64 GNU/Linux
conf.txt
SIGQUIT

@socol1
Copy link
Author

socol1 commented Sep 5, 2016

info is upload

@sparrc
Copy link
Contributor

sparrc commented Sep 5, 2016

@socol1 can you provide some details on the system you are running on? There is nothing very abnormal about the stack-trace that I can tell.

but, these are the instances that I would say are likely causing the most CPU usage (in order):

  1. 18 procstat plugins
  2. exec plugin running once every second (this might be the biggest contributor, as I have no idea what it's doing)
  3. 18 net_response plugins
  4. the 2 inputs.net plugins could be combined into a single instance

I would recommend trying running without the procstat plugins and see how that affects your CPU usage, as well as trying without the exec plugin.

I would also recommend, with the procstat plugin, to use .pid files. If you are not using pid files, then the plugin needs to search for the given executable patterns at each interval. When given a pid file, it simply needs to read the file.

@socol1
Copy link
Author

socol1 commented Sep 7, 2016

@phemmer thanks ,I'll try it.

@socol1 socol1 closed this as completed Sep 8, 2016
@sparrc
Copy link
Contributor

sparrc commented Sep 8, 2016

@socol1 why did you close the issue? if you solved it can you explain how?

@lin-credible
Copy link

#2533
@sparrc

@socol1
Copy link
Author

socol1 commented Mar 15, 2017

@phemmer sorry Recently changed jobs,I closed the following items:
1)exec plugin
2)procstat plugins

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

5 participants