# Performance tips wanted for one time logs import

**URL:** <https://discuss.elastic.co/t/performance-tips-wanted-for-one-time-logs-import/129118>\
**Category:** Elasticsearch\
**Created:** [April 23, 2018, 1:30pm UTC](https://discuss.elastic.co/t/performance-tips-wanted-for-one-time-logs-import/129118 "2018-04-23T13:30:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Aditya\_Kumar](https://avatars.discourse-cdn.com/v4/letter/a/e9bcb4/32.png) [@Aditya\_Kumar](https://discuss.elastic.co/u/Aditya_Kumar)\
**Post date:** [April 23, 2018, 1:30pm UTC](https://discuss.elastic.co/t/performance-tips-wanted-for-one-time-logs-import/129118/1 "2018-04-23T13:30:05Z")

</div>

I use an ELK stack to process sets of historical logs which I receive from customers in zipped up bundle.

In total there could be 2~3 million lines of logs which I want to import quickly so I can start analysing them in Kibana.

However these logs can take a long time to be fully processed by elasticsearch / kibana. I can see my index growing slowly and it could be 4 - 5 hours before everything is imported.

After I'm done with them I will delete them from elasticsearch, and later on import a new set.

Can anyone give me some configuration options that will help speed up the import of these logs?

I have 4 cores in my system and I notice my cpu is averaging 30-40% utilization during the import.

Is it logstash or elastic that does most of the heavy lifting? I want my CPU's to be working much harder!

---

<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:** [May 21, 2018, 1:30pm UTC](https://discuss.elastic.co/t/performance-tips-wanted-for-one-time-logs-import/129118/2 "2018-05-21T13:30:12Z")

</div>

Closed on May 21, 2018, 1:30pm UTC

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