# Understanding Memory CPU values with helm and OPensearch dashbaord

**URL:** <https://forum.opensearch.org/t/understanding-memory-cpu-values-with-helm-and-opensearch-dashbaord/21565>\
**Category:** OpenSearch\
**Tags:** configure\
**Created:** [September 20, 2024, 5:50am UTC](https://forum.opensearch.org/t/understanding-memory-cpu-values-with-helm-and-opensearch-dashbaord/21565 "2024-09-20T05:50:21Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Deepa](https://avatars.discourse-cdn.com/v4/letter/d/91b2a8/32.png) [@Deepa](https://forum.opensearch.org/u/Deepa)\
**Post date:** [September 20, 2024, 5:50am UTC](https://forum.opensearch.org/t/understanding-memory-cpu-values-with-helm-and-opensearch-dashbaord/21565/1 "2024-09-20T05:50:21Z")

</div>

**Versions** (relevant - OpenSearch/Dashboard/Server OS/Browser):

2.14.0

**Describe the issue** :

Am not able to understand configuration mentioned in helm chart and result when i get from DEvtools Get api query in opensearch dashbaord. AM pretty new to ECK and Opensearch. Please help me

**Configuration** :  
As per helm chart , Hot node configuration is  
replicas: 3  
pdb:  
enable: true  
minAvailable: 2  
diskSize: “750Gi”  
jvm: -Xmx5200M -Xms5200M  
nodeSelector:  
resources:  
requests:  
memory: “8Gi”  
cpu: 4  
limits:  
memory: “8Gi”  
cpu: 4

===WHen in Devtools using GET \_cat/allocation?v&s=disk.percent query ======

| shards | disk.indices | disk.used | disk.avail | disk.total | disk.percent | node |
| --- | --- | --- | --- | --- | --- | --- |
| 40 | 156.9gb | 156.9gb | 530.9gb | 687.9gb | 22 | opensearch-cluster-data-cold-2 |
| 40 | 156.1gb | 156.2gb | 531.7gb | 687.9gb | 22 | opensearch-cluster-data-cold-1 |
| 40 | 156.8gb | 156.8gb | 531gb | 687.9gb | 22 | opensearch-cluster-data-cold-0 |
| 40 | 158.9gb | 159gb | 528.9gb | 687.9gb | 23 | opensearch-cluster-data-warm-0 |
| 40 | 159.3gb | 159.3gb | 528.5gb | 687.9gb | 23 | opensearch-cluster-data-warm-1 |
| 40 | 159.1gb | 159.2gb | 528.7gb | 687.9gb | 23 | opensearch-cluster-data-warm-2 |
| 40 | 189.3gb | 191.3gb | 546.3gb | 737.6gb | 25 | opensearch-cluster-hot-data-1 |
| 40 | 152.4gb | 223.1gb | 514.5gb | 737.6gb | 30 | opensearch-cluster-hot-data-2 |
| 41 | 227.9gb | 230.5gb | 507.1gb | 737.6gb | 31 | opensearch-cluster-hot-data-0 |

Can explain me how this is matching.  
**Relevant Logs or Screenshots** :

---

<div class="post-metadata">

**Author:** ![pablo](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/pablo/32/10363_2.png) [@pablo](https://forum.opensearch.org/u/pablo)\
**Post date:** [September 20, 2024, 8:34am UTC](https://forum.opensearch.org/t/understanding-memory-cpu-values-with-helm-and-opensearch-dashbaord/21565/2 "2024-09-20T08:34:38Z")

</div>

@Deepa What is the exact question? Which part do you need an explanation for?

---

<div class="post-metadata">

**Author:** ![Deepa](https://avatars.discourse-cdn.com/v4/letter/d/91b2a8/32.png) [@Deepa](https://forum.opensearch.org/u/Deepa)\
**Post date:** [September 20, 2024, 9:35am UTC](https://forum.opensearch.org/t/understanding-memory-cpu-values-with-helm-and-opensearch-dashbaord/21565/3 "2024-09-20T09:35:57Z")

</div>

as per helm chart its shown as  
memory: “8Gi”  
cpu: 4

but as per GET API query it gives as

| shards | disk.indices | disk.used | disk.avail | disk.total | disk.percent | node |
| --- | --- | --- | --- | --- | --- | --- |
| 40 | 189.3gb | 191.3gb | 546.3gb | 737.6gb | 25 | opensearch-cluster-hot-data-1 |
| 40 | 152.4gb | 223.1gb | 514.5gb | 737.6gb | 30 | opensearch-cluster-hot-data-2 |
| 41 | 227.9gb | 230.5gb | 507.1gb | 737.6gb | 31 | opensearch-cluster-hot-data-0 |

So where is this memory of 8Gi being shown here , or is ther any unit convertion?  
Also which API query i can see for CPU value as 4 mentioned in helm chart

---

<div class="post-metadata">

**Author:** ![sebastian-thorn](https://avatars.discourse-cdn.com/v4/letter/s/958977/32.png) [@sebastian-thorn](https://forum.opensearch.org/u/sebastian-thorn)\
**Post date:** [September 20, 2024, 10:09am UTC](https://forum.opensearch.org/t/understanding-memory-cpu-values-with-helm-and-opensearch-dashbaord/21565/4 "2024-09-20T10:09:39Z")

</div>

Hi,

memory GB is not the same as disk GB, this is a fundamental difference.

Here you can find metrics on memory, [Nodes stats - OpenSearch Documentation](https://opensearch.org/docs/latest/api-reference/nodes-apis/nodes-stats/)

[What is the difference between memory and disk storage? (iu.edu)](https://kb.iu.edu/d/ahtx)

Best Regards  
Sebastian

---

<div class="post-metadata">

**Author:** ![pablo](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/pablo/32/10363_2.png) [@pablo](https://forum.opensearch.org/u/pablo)\
**Post date:** [September 27, 2024, 12:06am UTC](https://forum.opensearch.org/t/understanding-memory-cpu-values-with-helm-and-opensearch-dashbaord/21565/5 "2024-09-27T00:06:05Z")

</div>

@Deepa This section in values.yml refers to CPU cores and RAM.

```auto
resources:
  requests:
    cpu: "1000m"
    memory: "100Mi"

```

> <https://github.com/opensearch-project/helm-charts/blob/8a4f092fd0cdae5033eb468f77b0f4752e3d8bcc/charts/opensearch/values.yaml#L148>

Storage is defined as persistent volume in the persistence section of the values.yml file.

```auto
  size: 8Gi

```

> <https://github.com/opensearch-project/helm-charts/blob/8a4f092fd0cdae5033eb468f77b0f4752e3d8bcc/charts/opensearch/values.yaml#L220C1-L220C12>