# Advice to process events in elasticsearch

**URL:** <https://discuss.elastic.co/t/advice-to-process-events-in-elasticsearch/168190>\
**Category:** Elasticsearch\
**Created:** [February 13, 2019, 11:07am UTC](https://discuss.elastic.co/t/advice-to-process-events-in-elasticsearch/168190 "2019-02-13T11:07:26Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ganesh2303](https://avatars.discourse-cdn.com/v4/letter/g/57b2e6/32.png) [@Ganesh2303](https://discuss.elastic.co/u/Ganesh2303)\
**Post date:** [February 13, 2019, 11:07am UTC](https://discuss.elastic.co/t/advice-to-process-events-in-elasticsearch/168190/1 "2019-02-13T11:07:26Z")

</div>

Hi Team,  
Can anyone clear my doubt, we have stand-alone elasticsearch service is running and we are trying to parse 1 lakhs of record in 1s, is it possible to achieve that with good performance tuning.

Parsing is happening through postman with Go-lang

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [February 13, 2019, 11:37am UTC](https://discuss.elastic.co/t/advice-to-process-events-in-elasticsearch/168190/2 "2019-02-13T11:37:34Z")

</div>

That depends a lot on the size and complexity of your documents as well as the specification of the node. How you index it will also play a part.

---

<div class="post-metadata">

**Author:** ![Nagarjuna\_Gadikatla](https://avatars.discourse-cdn.com/v4/letter/n/94ad74/32.png) [@Nagarjuna\_Gadikatla](https://discuss.elastic.co/u/Nagarjuna_Gadikatla)\
**Post date:** [February 13, 2019, 11:41am UTC](https://discuss.elastic.co/t/advice-to-process-events-in-elasticsearch/168190/3 "2019-02-13T11:41:07Z")

</div>

What's your standalone server capacity.

---

<div class="post-metadata">

**Author:** ![Ganesh2303](https://avatars.discourse-cdn.com/v4/letter/g/57b2e6/32.png) [@Ganesh2303](https://discuss.elastic.co/u/Ganesh2303)\
**Post date:** [February 13, 2019, 11:44am UTC](https://discuss.elastic.co/t/advice-to-process-events-in-elasticsearch/168190/4 "2019-02-13T11:44:57Z")

</div>

500Gb Harddisk  
16GB RAM

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [February 13, 2019, 11:53am UTC](https://discuss.elastic.co/t/advice-to-process-events-in-elasticsearch/168190/5 "2019-02-13T11:53:09Z")

</div>

To ingest that number of documents per second, you will be sending large amounts of data to Elasticsearch in parallel. I therefore suspect you will need more RAM and a good amount of CPU to process all the documents. You will also most likely require fast local SSDs as indexing is very I/O intensive.

---

<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:** [March 13, 2019, 11:53am UTC](https://discuss.elastic.co/t/advice-to-process-events-in-elasticsearch/168190/6 "2019-03-13T11:53:32Z")

</div>

Closed on March 13, 2019, 11:53am UTC

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