# How does ece limit disk iops for es node? **URL:** \ **Category:** Elastic Cloud Enterprise (ECE)\ **Created:** [April 2, 2019, 2:10am UTC](https://discuss.elastic.co/t/how-does-ece-limit-disk-iops-for-es-node/174899 "2019-04-02T02:10:06Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![rockybean](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rockybean/32/11443_2.png) [@rockybean](https://discuss.elastic.co/u/rockybean)\ **Post date:** [April 2, 2019, 2:10am UTC](https://discuss.elastic.co/t/how-does-ece-limit-disk-iops-for-es-node/174899/1 "2019-04-02T02:10:06Z")
Hi, As we know, docker provides capability to limit disk iops by using 'blkio-weight' parameter. I notice ece set different 'blkio-weight' for different size es node. What is the strategy behind this? Thanks! ---
**Author:** ![Alex\_Piggott](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alex_piggott/32/11053_2.png) [@Alex\_Piggott](https://discuss.elastic.co/u/Alex_Piggott)\ **Post date:** [April 2, 2019, 4:51pm UTC](https://discuss.elastic.co/t/how-does-ece-limit-disk-iops-for-es-node/174899/2 "2019-04-02T16:51:27Z")
The relative weight of the different clusters is proportional to their capacity (which is how CPU shares are also calculated) Specifically, the calculation is something like `min(1000, 1024*(cluster_mem/total_allocator_memory)*120%)`, but that's an internal implementation detail subject to change. Alex ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 16, 2019, 5:06pm UTC](https://discuss.elastic.co/t/how-does-ece-limit-disk-iops-for-es-node/174899/3 "2019-04-16T17:06:23Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.