# Elasticsearch IOPS

**URL:** <https://discuss.elastic.co/t/elasticsearch-iops/265680>\
**Category:** Elasticsearch\
**Created:** [February 27, 2021, 5:47am UTC](https://discuss.elastic.co/t/elasticsearch-iops/265680 "2021-02-27T05:47:20Z")\
**Posts on this page:** 1\
**Showing post:** 9

<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 27, 2021, 10:02am UTC](https://discuss.elastic.co/t/elasticsearch-iops/265680/9 "2021-02-27T10:02:46Z")

</div>

Elasticsearch does generally not write very large segments sequentially, so your fio load is likely not very representative. I would recommend trying with a random read/write load instead as I would expect that to better match an Elasticsearch load pattern.

I recall having seen [issues with GlusterFS and NFS in the past](https://discuss.elastic.co/t/elk-on-docker-swarm-and-glusterfs-crash/127940) but [am not sure whether these issues persists](https://discuss.elastic.co/t/elastisearch-supports-glusterfs-and-rook-storage-system/193319).

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-iops/265680)._