Hi, On Mon, May 5, 2008 at 9:07 AM, Amos Shapira <[EMAIL PROTECTED]> wrote:
> Two questions: > > 1. Is this correct (that vserver will run more efficiently in that > situation)? Memory will be used more effectively, as free memory is shared. In case vservers use a shared storage (such as /home over here), memory cache for the storage blocks would get shared as well. 2. How does the vserver support in CentOS 5.1 compares to Xen? http://linux-vserver.org is fragile in sense of configuration. One must be very careful on network settings, so that no process would listen on 0.0.0.0IP number, as this would block the particular port for all vservers. Loopback interface is tricky as well. This is from my experience with 2 servers with 12 vservers on them. Coupled with the fact that there was no stable release since kernel 2.6.22, I would recommend to avoid the vserver technology for the time being. > I mean - with Xen it's just a matter of installing a couple of packages > and > off you go (especially now that the learning curve is mostly behind > me), with vserver - I can't even find a package which mentions this > string in its name or description ("yum search vserver"). So is it > worth the hassle? On debian the packages are in official repository. -- Arie > We expect to use the servers with very high IO (lots of disk access) and > CPU utilization. > > Thanks, > > --Amos > > ================================================================= > To unsubscribe, send mail to [EMAIL PROTECTED] with > the word "unsubscribe" in the message body, e.g., run the command > echo unsubscribe | mail [EMAIL PROTECTED] > > -- Arie
