6,534
edits
Changes
m
{{Stub}}
→cpuunits: intentation
</ol>
Applying a different diskinodes configuration is applied instantly and does not require a restart of the container.
You can also find the number of free inodes with
<pre>
# vzctl exec 123 df -i
</pre>
{{Note|shell does not support floating-point arithmetic, i.e. you can not use expressions like <code>$(( 220000*1.5 ))</code>. To use floating point, try <code>bc</code> instead, something like this: <code><nowiki>$(echo 220000*1.5 | bc)</nowiki></code>.}}
Add the three units, 1000+2000+3000 = 6000
* 101 gets 1000/6000 or 1/6th of the time. (16%)* 102 gets 2000/6000 or 1/3rd of the time. (34%)* 103 gets 3000/6000 or 1/2 of the time. (50%) To summarize: those units are proportional to each other. To say it more strict, to the sum of all CTs units, plus the host system, please don't forget that one. So indeed, units of 1 1 1 1 are the same as 200 200 200 200 or 8888 8888 8888 8888. You may wonder why there's the tool vzcpucheck, which returns an absolute number called the "power of the node". The thing is, when you move a CT from one box to another, it could be problematic if you use different scales and different CPUs. So vzcpucheck tries to work around that by inventing something called 'power of the node' which it gets from /proc/cpuinfo I guess (haven't checked it). If it shows a power of the node 10000 and you distribute that among all the CTs on the node, and then move one CT to another node which had cpuunits set in the same manner, that CT will have about the same CPU units it had on the old node.
=== cpulimit ===
In the rhel6 kernel the applied limit is divided between onlince CPUs proportionally and a busy CPU cannot borrow time from an idle one. I.e. with a 2 CPUs container and 100% limit set the usage of each CPU cannot exceed 50% in any case.
[[Category: Troubleshooting]]
