# How to improve io performance in elasticsearch?

**URL:** https://discuss.elastic.co/t/how-to-improve-io-performance-in-elasticsearch/65451
**Category:** Logstash
**Created:** [November 9, 2016, 8:22am UTC](https://discuss.elastic.co/t/how-to-improve-io-performance-in-elasticsearch/65451 "2016-11-09T08:22:11Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Evgeny\_Rachlenko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/evgeny_rachlenko/32/13037_2.png) [@Evgeny\_Rachlenko](https://discuss.elastic.co/u/Evgeny_Rachlenko)
#### Post date: [November 9, 2016, 8:22am UTC](https://discuss.elastic.co/t/how-to-improve-io-performance-in-elasticsearch/65451/1 "2016-11-09T08:22:11Z")

</div>

Hello ,

I've followed document explain well how to improve the io performance :  
[https://www.elastic.co/guide/en/elasticsearch/guide/current/indexing-performance.html](https://www.elastic.co/guide/en/elasticsearch/guide/current/indexing-performance.html)

but cluster still works too hards.

The question what if we create index nodes and use local SSD (x10 faster) ?  
we can probably use 2-3 indexing nodes and then just clone the indexes to the data nodes

Is it a convenient way of solving this problem ?

---

<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: [November 9, 2016, 8:27am UTC](https://discuss.elastic.co/t/how-to-improve-io-performance-in-elasticsearch/65451/2 "2016-11-09T08:27:26Z")

</div>

In order to optimising indexing performance, it is quite common to have different types of data nodes in the cluster. This is often referred to as the [Hot/Warm](https://www.elastic.co/blog/hot-warm-architecture) architecture. A subset of nodes equipped with fast, attached SSDs handle all the indexing and a lot of the querying of recent data, while nodes with larger amount of slower, spinning disks are used for long term storage and querying of older data. This can be a very efficient approach and is described in more detail in the blog post I linked to.

---

<div class="post-metadata">

### Author: ![Evgeny\_Rachlenko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/evgeny_rachlenko/32/13037_2.png) [@Evgeny\_Rachlenko](https://discuss.elastic.co/u/Evgeny_Rachlenko)
#### Post date: [November 9, 2016, 8:36am UTC](https://discuss.elastic.co/t/how-to-improve-io-performance-in-elasticsearch/65451/3 "2016-11-09T08:36:01Z")

</div>

> [@Christian\_Dahlqvist](#):
>
> In order to optimising indexing performance, it is quite common to have different types of data nodes in the cluster. This is often referred to as the Hot/Warm architecture. A subset of nodes equipped with fast, attached SSDs handle all the indexing and a lot of the querying of recent data, while nodes with larger amount of slower, spinning disks are used for long term storage and querying of older data. This can be a very efficient approach and is described in more detail in the blog post I linked to.

Christian, thank you very much 🙂 I'll try it :)))))

---

<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 7, 2016, 8:36am UTC](https://discuss.elastic.co/t/how-to-improve-io-performance-in-elasticsearch/65451/4 "2016-12-07T08:36:09Z")

</div>

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