# ElasticSearch report a strange os memory and search very slow,

**URL:** <https://discuss.elastic.co/t/elasticsearch-report-a-strange-os-memory-and-search-very-slow/111424>\
**Category:** Elasticsearch\
**Created:** [December 12, 2017, 7:48pm UTC](https://discuss.elastic.co/t/elasticsearch-report-a-strange-os-memory-and-search-very-slow/111424 "2017-12-12T19:48:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![akirafei](https://avatars.discourse-cdn.com/v4/letter/a/58956e/32.png) [@akirafei](https://discuss.elastic.co/u/akirafei)\
**Post date:** [December 12, 2017, 7:48pm UTC](https://discuss.elastic.co/t/elasticsearch-report-a-strange-os-memory-and-search-very-slow/111424/1 "2017-12-12T19:48:48Z")

</div>

Running ES in docker on a physical box with VMware ESXi6 CentOS 7 OS

Queries are currently taking more than 10 seconds to complete

\_cluster/stats reports a strange os memory:

total\_in\_bytes: 134778593280  
free\_in\_bytes: 2296119296  
used\_in\_bytes: 132482473984  
free\_percent: 2

Heap usage looks good.

 ![29 AM](https://us1.discourse-cdn.com/elastic/original/3X/2/d/2d9bfce55984370b383e357a63524c28e5753d4b.png)

However, when I try free command:

Mem total: 65809860  
Mem used: 36892596  
Mem available: 24905108

 ![37 AM](https://us1.discourse-cdn.com/elastic/original/3X/1/c/1cbbc4d4d732c9e9975c41dd6b04bbd89216a345.png)

the number reported by ES is strange to me.

Any idea? Thanks.

---

<div class="post-metadata">

**Author:** ![jasontedor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jasontedor/32/66992_2.png) [@jasontedor](https://discuss.elastic.co/u/jasontedor)\
**Post date:** [December 13, 2017, 4:06am UTC](https://discuss.elastic.co/t/elasticsearch-report-a-strange-os-memory-and-search-very-slow/111424/2 "2017-12-13T04:06:33Z")

</div>

You're looking at cluster stats which aggregates across your two nodes. Instead, look at node-level stats.

---

<div class="post-metadata">

**Author:** ![akirafei](https://avatars.discourse-cdn.com/v4/letter/a/58956e/32.png) [@akirafei](https://discuss.elastic.co/u/akirafei)\
**Post date:** [December 13, 2017, 6:45pm UTC](https://discuss.elastic.co/t/elasticsearch-report-a-strange-os-memory-and-search-very-slow/111424/3 "2017-12-13T18:45:42Z")

</div>

Thanks, yes figured out, the two nodes are on same machine, so it doubles the os memory.

---

<div class="post-metadata">

**Author:** ![akirafei](https://avatars.discourse-cdn.com/v4/letter/a/58956e/32.png) [@akirafei](https://discuss.elastic.co/u/akirafei)\
**Post date:** [December 13, 2017, 6:48pm UTC](https://discuss.elastic.co/t/elasticsearch-report-a-strange-os-memory-and-search-very-slow/111424/4 "2017-12-13T18:48:49Z")

</div>

However, still the search is super slow. About 10X slower than other direct physical boxes with same deployment configurations.

---

<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:** [January 10, 2018, 6:49pm UTC](https://discuss.elastic.co/t/elasticsearch-report-a-strange-os-memory-and-search-very-slow/111424/5 "2018-01-10T18:49:03Z")

</div>

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