Enter your OpenVZ Hardware Node (HN) details:

Memory

Enter your Hardware Node (HN) RAM and swap space values (in kB) here. The easist was to do this is by running the free command. Failing that you should(!) be able to get the values from /proc, e.g. egrep "(MemTotal|SwapTotal)" /proc/meminfo.
  1. kB
  2. kB

User Beancounters*

Paste your Hardware Node (HN) user beancounter information into the text box below. You can get this information from /proc/user_beancounters, e.g. cat /proc/user_beancounters. Alternatively you can use the Upload button to upload your user beancounter information directly. Click Calculate when you have filled in the required fields.

RAM Utilization By Container

VEID physpages (held) kmemsize (held) allsocketbuf (held)
No data supplied. Please enter your HN details on the Data tab. ---
Utilization
Utilization Level
Utilization levels from 0.8 to 1 are normal. Lower utilization means that the system is under-utilized, and, if other system resources and their commitment levels permit, the system can host more containers. By the nature of the accounting of physpages and other parameters, total RAM utilization can't be bigger than 1. Read more

Memory And Swap Space By Container

VEID kmemsize (limit) privvmpages (barrier) othersockbuf (limit)
No data supplied. Please enter your HN details on the Data tab. ---
Commitment
Total
Level
Commitment levels more than 1 means that the containers are guaranteed more memory than the system has. Such overcommitment is strongly not recommended, because in that case if all the memory is consumed, random applications, including the ones belonging to the host system, may be killed and the system may become inaccessible by ssh(1) and lose other important functionality. Read more

Allocated Memory By Container

VEID kmemsize (held) privvmpages (held) othersockbuf (held)
No data supplied. Please enter your HN details on the Data tab. ---
Commitment
Total
Level
Similar to the commitment level of memory plus swap space, this level should be kept below 1. If the level is above 1, it significantly increases the chance of applications being killed instead of being notified in event of system memory shortage. Read more

Limiting Memory Allocations By Container

VEID privvmpages (limit) percentage (of 60%)
No data supplied. Please enter your HN details on the Data tab. --
60 % Value
The bigger the level of memory allocation restrictions, the more chances are that applications will be killed instead of getting an error on next memory allocation in case the system experiences memory shortage. The levels ranging in 1.5–4 can be considered acceptable. Administrators can find experimentally the optimal setting for their load, basing on the frequency of messages “Out of Memory: killing process” in system logs, saved by klogd(8) and syslogd(8). However, for stability-critical applications, it's better to keep the level not exceeding 1. Read more

OpenVZ

The OpenVZ Utilization Calculator was put together to help visualize the data exposed by the user beancounters and compare it with the recommended usage as per the OpenVZ wiki.

OpenVZ OpenVZ is container-based virtualization for Linux. OpenVZ creates multiple secure, isolated containers (otherwise known as VEs or VPSs) on a single physical server enabling better server utilization and ensuring that applications do not conflict. Each container performs and executes exactly like a stand-alone server; a container can be rebooted independently and have root access, users, IP addresses, memory, processes, files, applications, system libraries and configuration files.

Changelog

  • 10th Jan 2010
    • Ordered VNs by ID
    • Removed HN from Limiting Memory Allocations Tab
  • 20th Dec 2009
    • Added file upload facility
    • Added more detailed parser error messages
    • RAM and swap defaults changed from 0 to empty