# Sequential write and random write for Elasticsearch

**URL:** <https://discuss.elastic.co/t/sequential-write-and-random-write-for-elasticsearch/118754>\
**Category:** Elasticsearch\
**Created:** [February 7, 2018, 6:14am UTC](https://discuss.elastic.co/t/sequential-write-and-random-write-for-elasticsearch/118754 "2018-02-07T06:14:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![lukekingbru](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/lukekingbru/32/25254_2.png) [@lukekingbru](https://discuss.elastic.co/u/lukekingbru)\
**Post date:** [February 7, 2018, 6:14am UTC](https://discuss.elastic.co/t/sequential-write-and-random-write-for-elasticsearch/118754/1 "2018-02-07T06:14:59Z")

</div>

For HDD, There is a huge performance difference between sequential write and random write.

1. I wonder if Elasticsearch also has this issue ? For instance, If I want to write 1M records, 1KB per record, into ES, how can I avoid random access as much as possible ?

2. What is the worst case which bring a lot of random access for ES?

Our ES running is on RAID-0

Thanks,

---

<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 7, 2018, 6:15am UTC](https://discuss.elastic.co/t/sequential-write-and-random-write-for-elasticsearch/118754/2 "2018-03-07T06:15:10Z")

</div>

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