-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/28/2014 03:47 PM, Nipun Arora wrote: > Hi folks, Hi Nipun!
> 1. --cpu-limit puts a limit on the max percentage of cpu that can > be used in the container. Exactly. 100% is a core, 200% is two cores and so on. > Does this also limit the number of processors the container has > access to? No, it does not. For that you need --cpus. For example: Defining --cpus 2 --cpulimit 100 results in processes being migrated around 2 cores with either a maximum of 50% for each core (if both cores are used at the same time) or 100% for one core (if only one core is used at the same time) or something in between. So, the resulting sum of both cores calculated does never exceed 100% (75%+25%=100%, or 10%+90%=100%, and so on...). > 2. --io-limit is a way to limit the I/O - How is this measured? > Both read+write combined? - --iolimit limits both, read and write. Read and write are combined. But(!), --iolimit never limits cached read/writes, only direct access or flushed data/access. - -- Best regards Kevin Holly - r...@hallowe.lt - http://hallowe.lt/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJUeLDkAAoJELAaqP3QtzpMep0IALp2f76W7581rgkA7+7FDi7U afqrCbn1pSxHaz+sjwXvaRHncrqznEWSaendDXhA7aGT1kM3PuYpvxrEGNIkooiW VNSoU/QyQmuflYIlTRvfiLaGh8Ol6pJ+j6L5vZX0UIDht04x9Q2MsMSgYnKRNDjM NKzOM52zFc7zMxR4Hd9jETLITUTUjpQX3k5BLfeJRZJZc+B3KoKI7tYpY52RAJ4Z Drp364VUI0XX/KVVC3jexfq9V7BDJUKWT6sqUMiWBEzI46D7e+neLbITohc0V0TD 8kHDeQT+Jna+l4rVIZxwUqV+DGyulz+HMdHAt8fjMe6XA1IWaEdJnF5X8cF34IQ= =kYhh -----END PGP SIGNATURE----- _______________________________________________ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
