# Monitoring DISKIO for elasticsearch in Windows

**URL:** <https://discuss.elastic.co/t/monitoring-diskio-for-elasticsearch-in-windows/56063>\
**Category:** Elasticsearch\
**Created:** [July 21, 2016, 6:16am UTC](https://discuss.elastic.co/t/monitoring-diskio-for-elasticsearch-in-windows/56063 "2016-07-21T06:16:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Karthik\_Ramachandran](https://avatars.discourse-cdn.com/v4/letter/k/f19dbf/32.png) [@Karthik\_Ramachandran](https://discuss.elastic.co/u/Karthik_Ramachandran)\
**Post date:** [July 21, 2016, 6:16am UTC](https://discuss.elastic.co/t/monitoring-diskio-for-elasticsearch-in-windows/56063/1 "2016-07-21T06:16:52Z")

</div>

How do I say my DISK IO is a bottleneck?  
I'm using AZURE VMs for elastic search in Windows OS. In each VM, I attach a data drive (F:), which is derived of storage pool using 2 physical disks. These disks are not SSD's. When I restart the node, I see lot of elastic search operations going on with disks performing assignment of shards. I see the disk reads/writes @ around 30MB/Sec. Is it expected. The node has around 120GB of data with 23 shards.

The confusion is because according to azure documentation  
[https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/](https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/), if I use 2 disks (2blobs) it should be 60+60 120MBPS at the rate of 1000 requests/sec.

Kindly clarify

---

<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:** [July 5, 2017, 10:33pm UTC](https://discuss.elastic.co/t/monitoring-diskio-for-elasticsearch-in-windows/56063/2 "2017-07-05T22:33:49Z")

</div>