Avdi Grimm on 2009-07-10
Some explanation of VServer overhead (or lack thereof)
Avdi Grimm's personal annotations on this page
Avdigrimm bookmarked
on 2009-07-10
-
- A vserver does not use any resource by itself. There is no "invisible" overhead for each vserver. The overhead comes from the tasks you are running inside the vserver. You can expect the exact same performance in a vserver as compared to the root server. There is no overhead. Processes running in the vserver are talking directly to the kernel. Only few system calls (kill for one) have special checks to insure processes isolation.
- A vserver does not use any resource by itself. There is no "invisible" overhead for each vserver. The overhead comes from the tasks you are running inside the vserver. You can expect the exact same performance in a vserver as compared to the root server. There is no overhead. Processes running in the vserver are talking directly to the kernel. Only few system calls (kill for one) have special checks to insure processes isolation.
- In addition, using this setup libraries and binaries are read-only and shared in a "unified" environment. This allows us to have multiple instances of libraries and binaries installed with little disk space and memory footprint used. For example, a glibc using up 5 megabytes used in 10 vservers only contributes .5MB to each, and reduces the memory footprint by a factor of 10.
- In addition, using this setup libraries and binaries are read-only and shared in a "unified" environment. This allows us to have multiple instances of libraries and binaries installed with little disk space and memory footprint used. For example, a glibc using up 5 megabytes used in 10 vservers only contributes .5MB to each, and reduces the memory footprint by a factor of 10.
-
Avdigrimm on 2009-07-10Some explanation of VServer overhead (or lack thereof)
This link has been bookmarked by 1 people . It was first bookmarked on 10 Jul 2009, by Avdi Grimm.
-
-
- A vserver does not use any resource by itself. There is no "invisible" overhead for each vserver. The overhead comes from the tasks you are running inside the vserver. You can expect the exact same performance in a vserver as compared to the root server. There is no overhead. Processes running in the vserver are talking directly to the kernel. Only few system calls (kill for one) have special checks to insure processes isolation.
- A vserver does not use any resource by itself. There is no "invisible" overhead for each vserver. The overhead comes from the tasks you are running inside the vserver. You can expect the exact same performance in a vserver as compared to the root server. There is no overhead. Processes running in the vserver are talking directly to the kernel. Only few system calls (kill for one) have special checks to insure processes isolation.
- In addition, using this setup libraries and binaries are read-only and shared in a "unified" environment. This allows us to have multiple instances of libraries and binaries installed with little disk space and memory footprint used. For example, a glibc using up 5 megabytes used in 10 vservers only contributes .5MB to each, and reduces the memory footprint by a factor of 10.
- In addition, using this setup libraries and binaries are read-only and shared in a "unified" environment. This allows us to have multiple instances of libraries and binaries installed with little disk space and memory footprint used. For example, a glibc using up 5 megabytes used in 10 vservers only contributes .5MB to each, and reduces the memory footprint by a factor of 10.
-
Public Stiky Notes
Would you like to comment?
Join Diigo for a free account, or sign in if you are already a member.