Editing OpenVZ vs. Virtuozzo
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
| − | + | == Comparison == | |
| + | |||
| + | Many may wonder what exactly the difference between OpenVZ and Virtuozzo is.<br/> | ||
| + | Virtuozzo is based off OpenVZ, which means it adds a few features. Which are that? | ||
| + | |||
| + | * Management interface (GUI) | ||
| + | * Resource management | ||
| + | * SLM memory management, while OpenVZ uses UBC ("Unified Buffer Cache"), [[OpenVZ vs. Virtuozzo#SLM vs. UBC|see below for a comparison]]. | ||
| + | * VZFS (allows for disk and memory savings very similiar to Linux-VServer's copy-on-write system called "unification") | ||
| + | * Commercial support | ||
| + | |||
| + | OpenVZ is mostly run by Parallels (owner of Virtuozzo) employees, who maintain OpenVZ as the core functionality of Virtuozzo. | ||
| + | |||
| + | == SLM vs. UBC == | ||
| + | An example would be: With UBC a VPS may be limited to 128 iptables entries. With SLM you can create thousands of iptables entries up to their global RAM limit. | ||
| + | See bottom of http://www.tektonic.net/vz.html for a description of the SLM technology. | ||
