# Options to compress topbeat index

**URL:** <https://discuss.elastic.co/t/options-to-compress-topbeat-index/61894>\
**Category:** Beats\
**Created:** [September 30, 2016, 5:05am UTC](https://discuss.elastic.co/t/options-to-compress-topbeat-index/61894 "2016-09-30T05:05:34Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![talk2cshah](https://avatars.discourse-cdn.com/v4/letter/t/8e7dd6/32.png) [@talk2cshah](https://discuss.elastic.co/u/talk2cshah)\
**Post date:** [September 30, 2016, 5:05am UTC](https://discuss.elastic.co/t/options-to-compress-topbeat-index/61894/1 "2016-09-30T05:05:34Z")

</div>

Hi Team,

We have topbeat agent running on 10 systems and 10 second pulse.  
It is further configured for process, CPU and system logs. the average payload per 10s is 150KB ~300KB resulting in 300 MB per server per day resulting 3GB+ data per day.

I understand that the indexes are already compressed . Are there any other options to further reduce the index size...

**Note** : I am aware of archival backup and restore but not intending to implement due to project requirements.  
Also do we have benchmarks of topbeat compared to other agents in terms of data, resource utilization etc. Kindly point if any

Look forward to suggestions.

Regards,

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [September 30, 2016, 5:21am UTC](https://discuss.elastic.co/t/options-to-compress-topbeat-index/61894/2 "2016-09-30T05:21:57Z")

</div>

ES compresses by default, but take a look at [https://www.elastic.co/guide/en/elasticsearch/reference/2.4/index-modules.html#index-codec](https://www.elastic.co/guide/en/elasticsearch/reference/2.4/index-modules.html#index-codec)

---

<div class="post-metadata">

**Author:** ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)\
**Post date:** [October 3, 2016, 8:23am UTC](https://discuss.elastic.co/t/options-to-compress-topbeat-index/61894/3 "2016-10-03T08:23:58Z")

</div>

If you are using elasticsearch 5.0 with metricbeat the events will take less space as `scaled_floats` were introduced which are especially useful for percentage values.

---

<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:** [October 21, 2016, 5:05am UTC](https://discuss.elastic.co/t/options-to-compress-topbeat-index/61894/4 "2016-10-21T05:05:40Z")

</div>

This topic was automatically closed after 21 days. New replies are no longer allowed.