Problem
VPs capacity problems caused by 32-bit windows without paging memory limit
Solution
On a 32-bit Windows system, the main parameter restricting the number of VPs is "non-Paging memory"
Open your job manager in windows, select the performance tab, View "core memory", and view "not paging"
In 32-bit windows, this parameter cannot exceed 256 MB, that is, 262144
When it comes to this parameter, Windows becomes very unstable.
This restriction does not exist for Windows that use x86-64 architectures.
Therefore, the maximum number of windows ozzo servers is not the physical memory size.
But the limitation of this parameter.
For example, the server has 4 GB of physical memory and automatically allocates 6 GB of virtual memory as required by windows.
At this time, you can create a VPs of MB to MB of memory of about 60 to 80
However, there are basically no applications in each VPs at this time.ProgramIn
VPs occupies a small amount of memory.
When the VPs goes online and carries user data, the memory usage increases gradually.
At this time, the number of non-Paging memory for Windows core memory gradually approaches the limit of MB.
Windows is unstable now.
For vzwin351sp1, SP1 provides independent terminal services for each VPs.
Therefore, VPs consumes more resources.
This also results in the non-Paging memory approaching 256 MB as soon as possible
Therefore, it is used in production environments in vzwin351sp1 scenarios.
If the server is a 32-bit Windows environment with 4 GB physical memory and 6 GB virtual memory
Creating 30 VPs is a relatively safe and secure capacity.
To open more VPs, you need to use the x86-64 version of Windows
At the same time, there is no such limit in Linux, 32-bit Linux can reach a high capacity
From vzwin35138, the non-Paging memory Parameter Restriction function is added. You can specify the non-Paging memory for each VPs.
But it can only be set in the command line. The method is as follows:
Vzctl set 101 -- nonpagedpoollimit 20
101 indicates the VPs ID, and 20 indicates 20 mb.