# Instrumenting CPU usage of logstash and elasticsearch

**URL:** <https://discuss.elastic.co/t/instrumenting-cpu-usage-of-logstash-and-elasticsearch/111460>\
**Category:** Elasticsearch\
**Created:** [December 13, 2017, 12:01am UTC](https://discuss.elastic.co/t/instrumenting-cpu-usage-of-logstash-and-elasticsearch/111460 "2017-12-13T00:01:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Supermathie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/supermathie/32/44936_2.png) [@Supermathie](https://discuss.elastic.co/u/Supermathie)\
**Post date:** [December 13, 2017, 12:01am UTC](https://discuss.elastic.co/t/instrumenting-cpu-usage-of-logstash-and-elasticsearch/111460/1 "2017-12-13T00:01:06Z")

</div>

We made some changes to our elasticsearch install (upgrading to 6, enabling beats, pipeline changes...) and the CPU usage of our logstash/elastic server has shot up:

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/6/8/68ecd0743130c9a254584f6a059884606e3f57ae.png)

The CPU% usage is roughly split between logstash and elasticsearch.

How can we instrument the stack to determine WHY it's using so much CPU (ingest rate of approximately 5K/s) and change how we're doing things (if possible) to use less CPU?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 10, 2018, 12:01am UTC](https://discuss.elastic.co/t/instrumenting-cpu-usage-of-logstash-and-elasticsearch/111460/2 "2018-01-10T00:01:06Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.