# Help to optimize processing

**URL:** https://community.graylog.org/t/help-to-optimize-processing/9200
**Category:** Graylog Central (peer support)
**Created:** [March 1, 2019, 1:45pm UTC](https://community.graylog.org/t/help-to-optimize-processing/9200 "2019-03-01T13:45:43Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![tmacgbay](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/tmacgbay/32/3878_2.png) [@tmacgbay](https://community.graylog.org/u/tmacgbay)
#### Post date: [March 1, 2019, 2:24pm UTC](https://community.graylog.org/t/help-to-optimize-processing/9200/2 "2019-03-01T14:24:55Z")

</div>

You may want to consider moving your Elasticsearch to another machine so it can handle the influx from GL. I used elasticdump ([https://www.npmjs.com/package/elasticdump](https://www.npmjs.com/package/elasticdump)) to do this since I don’t have resources to start up a elastic cluster. There are also a lot of other posts on optimizing in the GL community if you search for them… here is one, though they have clusters rather than docker instances. [Status Green, all systems go. How to optimize?](https://community.graylog.org/t/status-green-all-systems-go-how-to-optimize/2170)

---

_[View the full topic](https://community.graylog.org/t/help-to-optimize-processing/9200)._