Article ID: 122299, created on Jul 9, 2014, last review on Jun 17, 2016

  • Applies to:
  • Plesk 12.5 for Linux
  • Plesk 11.5 for Linux
  • Virtuozzo 6.0
  • Virtuozzo containers for Linux 4.7


High memory usage can be observed inside of a container, however there are no processes that are consuming this amount of memory:

[root@container ~]# free -m
             total       used       free     shared    buffers     cached
Mem:          4096       4088          7          0          0        110
-/+ buffers/cache:       3977        118
Swap:            0          0          0

Container is stable, processes are not generating "Out of Memory" events.

Checking /proc/user_beancounters inside of container shows that container is using high amount of dcachesize resource:

[root@container ~]# egrep 'dcachesize|resource' /proc/user_beancounters
       uid  resource                     held              maxheld              barrier                limit              failcnt
            dcachesize             3987513652           3987653040  9223372036854775807  9223372036854775807                    0

/proc/meminfo shows that most of consumed memory is accounted under Slab and SReclaimable:

[root@container ~]# cat /proc/meminfo | egrep 'MemTotal|MemFree|Slab|SReclaimable'
MemTotal:        4194304 kB
MemFree:            7824 kB
Slab:            3907088 kB
SReclaimable:    3894060 kB


Memory accounted in Slab and in SReclaimable is considered as cached, and it will be freed upon request. Big amount of cache in slabs is generated by nginx web server running inside of a container.


This memoery is reclaimable, thus there is nothing to worry about, it will be freed upon request and it will not cause stability issues for the container. It can be considered a cosmetic issue caused by nginx.

If it is necessary to avoid this behavior, it is possible to limit dcachesize to a smaller amount, e.g. 256 Mb, using following command:

# vzctl set <CTID> --dcachesize 268435456:295279001 --save

Note!: If container's memory management schema is SLM you won't be able to control dcachesize parameter. Set it to ubc or all to control dcachesize consumption.

# vzctl set <CTID> --save --slmmode ubc

Container must be restarted after changing memory management scheme.

You may learn more about dcachesize and other UBC resources in the following KB article:

112807 - UBC resources in Parallels Virtuozzo Containers for Linux

Search Words


migration slab

Memory usage in container is growing with no apprent consumption by running programs



memory resource issue

ram usage

memory leak

e8e50b42231236b82df27684e7ec0beb 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f c62e8726973f80975db0531f1ed5c6a2 0dd5b9380c7d4884d77587f3eb0fa8ef 0c05f0c76fec3dd785e9feafce1099a9 a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c 29d1e90fd304f01e6420fbe60f66f838 742559b1631652fadd74764ae8be475e e335d9adf7edffca6a8af8039031a4c7 01bc4c8cf5b7f01f815a7ada004154a2 0a53c5a9ca65a74d37ef5c5eaeb55d7f

Email subscription for changes to this article
Save as PDF