# SAN storage - I/O values

**URL:** <https://discuss.elastic.co/t/san-storage-i-o-values/376474>\
**Category:** Elasticsearch\
**Created:** [March 27, 2025, 12:36pm UTC](https://discuss.elastic.co/t/san-storage-i-o-values/376474 "2025-03-27T12:36:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![stephanenm](https://avatars.discourse-cdn.com/v4/letter/s/439d5e/32.png) [@stephanenm](https://discuss.elastic.co/u/stephanenm)\
**Post date:** [March 27, 2025, 12:36pm UTC](https://discuss.elastic.co/t/san-storage-i-o-values/376474/1 "2025-03-27T12:36:42Z")

</div>

Hello all,  
I am currently in charge to about find a storage system than can works with Elastic solutions. I need to have this storage system on prem so any cloud services is forbiden.  
I have read that Objet storage or NFS are the supported protocols but i can't find any documentation about the recommended I/O bandwith.

I need this inforation because all vendor ask the same question: What is the I/O recommended by Elastic.

Can someone helps me?

---

<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:** [March 27, 2025, 12:54pm UTC](https://discuss.elastic.co/t/san-storage-i-o-values/376474/2 "2025-03-27T12:54:43Z")

</div>

Object storage is as far as I know only supported for snapshots or searchable snapshots. The [official documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html#_node_data_path_settings) provides guidance on the behaviour your NFS file system must support if you choose to use that.

When it comes to performance it will depend on your use case and requirements so it is hard to give any general numbers. Note that both [the official guide on optimising indexing speed](https://www.elastic.co/guide/en/elasticsearch/reference/current/tune-for-indexing-speed.html#indexing-use-faster-hardware) as well as the [guide on optimising search speed](https://www.elastic.co/guide/en/elasticsearch/reference/current/tune-for-search-speed.html#search-use-faster-hardware) do recommend using local SSDs or storage with equivalent throughput and latency.

---

<div class="post-metadata">

**Author:** ![RainTown](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/raintown/32/140206_2.png) [@RainTown](https://discuss.elastic.co/u/RainTown)\
**Post date:** [March 27, 2025, 1:49pm UTC](https://discuss.elastic.co/t/san-storage-i-o-values/376474/3 "2025-03-27T13:49:45Z")

</div>

> [@stephanenm](#):
>
> I have read that Objet storage or NFS are the supported protocols

Where did you read that? It’s not accurate.

Broadly speaking , elasticsearch itself expects to be reading from and writing to a filesystem. Not object storage. NFS would be my last file system of choice, I would much prefer locally mounted file systems.

Is your solution going to have physical or virtual elasticsearch servers ? What sort of IO did your proof of concept system use? What sort of indexing and query footprint does your solution require?

You have to know wayyyy more than you’ve put in the question to be at the point of considering buying anything. I hope.