Linked by Thom Holwerda on Tue 26th Dec 2006 12:15 UTC, submitted by falko
Permalink for comment 196215
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2006-11-19
OpenVZ has clear advantages if you only need seperate environments in the same OS:
* There are finer controls for resource sharing
* It allows much higher density (hundreds of zones in a physical machine).
* Zones are much smaller than virtual machines (eg ~100MB zone versus ~500MB regular install)
* There is little I/O and network overhead
* You do not have to worry about details like synchronizing time, upgrading kernel, etc that you should in virtual machines.
So as long as sharing one kernel is sufficient for your job, OpenVZ is a better alternative than Xen or VMware.
Edited 2006-12-26 13:02