Difference between revisions of "Containers/Guarantees for resources"

From OpenVZ Virtuozzo Containers Wiki
Jump to: navigation, search
(No difference)

Revision as of 09:31, 15 September 2006

This page describes how guarantees for resources can be implemented.

How to guarantee a guarantee

It's not obvious at the first glance, but there are only two ways how a guarantee can be provided:

  1. reserving desired amount in advance
  2. limiting consumers to keep some amount free

The first way has the followong disadvantages:

reserving is impossible for certain resources
such resources as CPU time, disk or network bandwidth and similar can not be just reserved as theirs amount instatntly increases;
reserving is essentially a limit, but much more strict
cutting off X megabytes from RAM implies that all the rest groups are limited in theis RAM consumption;
reserving reduces containers density on the node
if one wants to run some identical containers each requiring 100Mb on 1Gb system reservations can be done for 10 only and starting the 11th becomes impossible.

On the other hand limiting of containers can provide guarantees for them as well.

Providing a guarantee through limiting

The idea of getting a guarantee is simple:

if any group requires a units of resource from units available then limiting all the rest groups with units provides a desired guarantee

For groups in the system this implies solving a linear equation set to get limits like this:

In a matrix form this looks like

where


and thus the solution is


Skipping boring calculations, the reverse matrix is

This solutions looks huge, but the vector is calculated in time:

void calculate_limits(int N, int *g, int *l)
{
        int sum;

        sum = 0;
        for (i = 0; i < N; i++)
                sum += g[i];
        for (i = 0; i < N; i++)
                l[i] = sum - (R - g[i]) - (N - 2) * (R - g[i]);
}