0 Replies Latest reply on Dec 12, 2018 2:50 AM by Czernobog

    VCSA 6.5 - memory allocation inconsistencies

    Czernobog Hot Shot

      Following some performance issues I have checked the memory allocation on some of my VCSA's. The active memory usage seems to be within limits, however there are inconsistencies in the output of the different monitoring tools.

      We have assigned 48GB physical memory to the appliance. The appliance is an upgraded 6.0 VCSA, a 'large' deployment and we are within limits of the sizing recommendations (<1000 hosts, <10000 vms), with external PSCs.

      Here's the command output:

       

      This one looks good:

      root@vcsa [ ~ ]# free -m
                    total        used        free      shared  buff/cache   available
      Mem:          48294       12085        9336        2279       26872       33606
      Swap:         52215           0       52215
      

       

      edit: Here's the output from top:

                 

      PIDUSERPRNIVIRTRES%CPU%MEMTIME+SCOMMAND
      3659vpxd2008642.3m2.309g13.84.91128:07Svpxd
      54010vpostgr+2002442.6m2.210g0.74.78:03.53Spostgres
      1664vpostgr+2002377.3m2.162g0.04.613:15.61Spostgres
      1665vpostgr+2002376.4m1.956g0.04.10:36.64Spostgres
      54011vpostgr+2002442.6m1.799g0.03.80:45.09Spostgres
      1637vsphere+20011.481g1.446g0.73.179:39.94Svsphere-client.
      1629vsphere+20011.411g1.197g1.32.549:37.24Svsphere-ui.laun
      2585root20010.149g913.2m0.71.957:05.21Svmware-vpxd-svc
      4455content+2009623.1m848.8m0.01.824:08.65Svmware-content-
      4450root20012.064g622.3m1.31.363:36.82Svmware-sps.laun
      2584vapiEnd+2008237.6m617.2m0.71.343:36.80Svmware-vapi-end
      5361updatem+20017.146g589.1m0.01.210:52.27Sjava
      58548vpostgr+2002381.5m503.0m0.01.00:02.56Spostgres
      1608root2004382.2m442.9m0.00.912:27.50Svmware-cm.launc
      4467perfcha+2008273.7m426.4m0.00.910:23.85Svmware-perfchar

       

      The dynamic allocation seems to work too:

       

      root@vcsa [ ~ ]# cloudvm-ram-size -l
      vmcad                =      224
      vmafdd               =       71
      vmware-rbd-watchdog  =      100
      applmgmt             =      376
      vmware-vsan-health   =      117
      vmware-vsm           =      273
      vmware-sps           =     3476
      vmware-stsd          =     1678
      vmware-vpostgres     =     4334
      vmware-eam           =      323
      vmware-sts-idmd      =      483
      vmware-mbcs          =      128
      vcha                 =       46
      vmware-vmon          =        5
      vmware-statsmonitor  =       10
      vmware-perfcharts    =     1704
      vsphere-client       =     2510
      vmonapi              =       15
      vmware-cm            =      574
      vmware-rhttpproxy    =      152
      vmware-imagebuilder  =       50
      vmware-sca           =      128
      vmware-vpxd          =    19330
      vsphere-ui           =     2510
      vmware-vapi-endpoint =      256
      vmware-content-library =      887
      vmdnsd               =       72
      vmware-updatemgr     =     1046
      vmware-vpxd-svcs     =     1459
      OS                   =     5925
      vmware-netdumper     =       20
      TOTAL(MB)            =    48282
      

       

      Now, the output from cloudvm-ram-size -S is what is weird, because it seems we would need to increate the physical RAM to over 70GB, to meet the service needs:

       

      root@vcsa [ ~ ]# cloudvm-ram-size -S | egrep 'Service-Name|LinuxKernel|vpxd|vsphere-client|vsphere-ui|postgres|TOTAL'
      Service-Name            AllocatedMB     MaxMB CurrentMB  Curr-RSS    Cache  MapFiles   MemoryLimit
      LinuxKernel                      -1     35314     35592         0      652         5 8796093022207
      vmware-vpostgres               4334     13854     13842       178    13663      2283 8796093022207
      vpxd                             -1      4005      3399      2287     1111        68 8796093022207
      vpxd-svcs                        -1       972       958       915       42         2 8796093022207
      vsphere-client                 2510      2428      2112      1536      576         0 8796093022207
      vsphere-ui                     2510      2093      1828      1286      541         0 8796093022207
      TOTAL(RAM=48294MB)             9821     70626     70530     11642    24413      2548 8796093022207
      

       

      The 'AllocatedMB' value is inconsistent, with what cloudvm-ram-size -l delivers. Why is that?

      Schloud I increase the memory allocation by hand with cloudvm-ram-size -C ?

       

      added top output