# Elastic log Events ingest rate optimization

**URL:** <https://discuss.elastic.co/t/elastic-log-events-ingest-rate-optimization/319440>\
**Category:** Elasticsearch\
**Created:** [November 21, 2022, 12:11pm UTC](https://discuss.elastic.co/t/elastic-log-events-ingest-rate-optimization/319440 "2022-11-21T12:11:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![abkonred](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@abkonred](https://discuss.elastic.co/u/abkonred)\
**Post date:** [November 21, 2022, 12:11pm UTC](https://discuss.elastic.co/t/elastic-log-events-ingest-rate-optimization/319440/1 "2022-11-21T12:11:56Z")

</div>

Hello Team,

I have ingested the data around 14.7GB, it took me around 29 minutes (From Filebeat-Logstash-Elasticsearch)to load the complete data. and later on next day the shard has been compressed to 10.5 GB.

could you please confirm below

whether elastic has compressing data method?  
What is the Data transfer rate in Elasticsearch if we are having 64GB RAM and 32core CPU)?

As we are planning from splunk to ELK, how to optimize and tune to increase the ingestion speed rate.

**Current Hardware specifications.** (Elasticsearch, logstash, Kibana)  
CPU- 16core  
RAM-32GB  
OS Disk Size-120GB

Thanks,  
Abhishek

---

<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:** [December 19, 2022, 12:12pm UTC](https://discuss.elastic.co/t/elastic-log-events-ingest-rate-optimization/319440/2 "2022-12-19T12:12:25Z")

</div>

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