How Physical memory is calculated in CDM probe

book

Article ID: 197727

calendar_today

Updated On:

Products

NIMSOFT PROBES DX Infrastructure Management

Issue/Introduction

We received the attached alarm from UIM, when we checked on server we got below output

[[email protected] ~]# cat /proc/meminfo

MemTotal:       32847836 kB

MemFree:          182980 kB

MemAvailable:   11598284 kB

Buffers:               0 kB

Cached:           982728 kB

SwapCached:            0 kB

Active:         19578128 kB

Inactive:         567528 kB

Active(anon):   19163984 kB

Inactive(anon):      240 kB

Active(file):     414144 kB

Inactive(file):   567288 kB

Unevictable:           0 kB

Mlocked:               0 kB

SwapTotal:             0 kB

SwapFree:              0 kB

Dirty:               176 kB

Writeback:             0 kB

AnonPages:      19162928 kB

Mapped:            63656 kB

Shmem:              1296 kB

Slab:           12159580 kB

SReclaimable:   10658356 kB

SUnreclaim:      1501224 kB

KernelStack:        8928 kB

PageTables:        47720 kB

NFS_Unstable:          0 kB

Bounce:                0 kB

WritebackTmp:          0 kB

CommitLimit:    16423916 kB

Committed_AS:   19296832 kB

VmallocTotal:   34359738367 kB

VmallocUsed:      204084 kB

VmallocChunk:   34359341052 kB

HardwareCorrupted:     0 kB

AnonHugePages:   7002112 kB

HugePages_Total:       0

HugePages_Free:        0

HugePages_Rsvd:        0

HugePages_Surp:        0

Hugepagesize:       2048 kB

DirectMap4k:      147328 kB

DirectMap2M:     8241152 kB

DirectMap1G:    27262976 kB

Environment

Release : 9.0.2

Component : UIM - CDM WITH IOSTAT

cdm 6.50

Resolution

The amount of physical memory used is based on the formula:

MemTotal - MemFree - Buffers – Cached. This is because buffers and cached data are instantly available to any process which requests more memory.

As per your data:

32847836  - 182920 - 0 - 982728 which equals-> 31,682,188.

31,682,188 divided by 32847836 is .9645137049515225‬ which is approx. 96%

Note that you will very likely see a small difference in the values in meminfo and the QOS metric. Memory usage is a constantly shifting value and the probe will have collected data at a slightly different time to when you viewed the meminfo file.