Changes

Jump to: navigation, search

FAQ

2,373 bytes added, 15:25, 18 April 2008
General: more q/a added
===== What is a container (Virtual Environment, Virtual Private Server, VPS, VE)? =====
:See [[Container]].
 
===== What are highlights of OpenVZ technology? =====
In short, OpenVZ is the only highly scalable virtualization technology with near-zero overhead, strong isolation and rapid customer provisioning that's ready for production use right now. Deployment of OpenVZ improves efficiency, flexibility and quality of service in the enterprise environment.
===== Who needs OpenVZ? How it can be used? =====
===== How is OpenVZ updated and why it is secure? =====
:See [[Security]].
 
===== How scalable is OpenVZ? =====
 
OpenVZ technology scales up pretty well - we've tested it on machines up to 8 CPU and up to 64 GB of RAM. Besides, a single container could be scaled up from taking a little fraction of available resources up to all resources available dynamically - you do not even have to restart the container.
 
===== How OpenVZ improves efficiency of services? =====
 
For existing hardware, OpenVZ allows to utilize its processing power better by improving average load from 3-5% to at least 30-50%, while still providing ability to handle peak loads. To decrease complexity, OpenVZ provides standardized and centralized server management, logically decoupled from actual hardware. And when its time to buy new servers, you can now use few more powerful servers instead of many little ones — with added benefits of better reliability, better peak performance and typically longer lifespan.
 
===== How OpenVZ improves flexibility of services? =====
 
By providing unified scalable platform with such unique features as rapid application and updates provisioning. Each container is hardware independent and can be moved to another OpenVZ-based system in seconds over the network. This allows for ease of hardware maintenance (move out all containers and do whatever you need with the box) and improved availability (keep a synchronized copy of your container elsewhere and start it up when primary service failed). If your old box is not able to cope with peak load anymore, just move your containers to a new one.
 
===== What is a performance overhead? =====
 
Near zero. There is no emulation layer, only security isolation, and all checking is done on the kernel level without context switching.
 
===== What are performance expectations? =====
 
Peak performance is achieved when only one container has active tasks. In this case, it could use 100% of available resources: all CPUs, all physical memory, all disk and network bandwidth. OpenVZ is not limiting you to a single-CPU virtual machine.
===== I want to show my appreciation to OpenVZ and put some logo to my site. Where to get it? =====

Navigation menu