Open main menu

OpenVZ Virtuozzo Containers Wiki β

Difference between revisions of "Containers/Guarantees for resources"

< Containers
m (Protected "Containers/Guarantees for resources" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite)))
 
(16 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 
[[Category:UBC]]
 
[[Category:UBC]]
 +
[[Category:Containers]]
  
 
This page describes how guarantees for resources can be implemented.
 
This page describes how guarantees for resources can be implemented.
Line 77: Line 78:
 
{
 
{
 
         int sum;
 
         int sum;
 +
        int i;
 +
 +
        if (N == 1) {
 +
                l[0] = R;
 +
                return;
 +
        }
  
 
         sum = 0;
 
         sum = 0;
 
         for (i = 0; i < N; i++)
 
         for (i = 0; i < N; i++)
                 sum += g[i];
+
                 sum += R - g[i];
 
         for (i = 0; i < N; i++)
 
         for (i = 0; i < N; i++)
                 l[i] = sum - (R - g[i]) - (N - 2) * (R - g[i]);
+
                 l[i] = (sum - (R - g[i]) - (N - 2) * (R - g[i]))/(N - 1);
 
}
 
}
 
</pre>
 
</pre>
  
= Disadvantages of this approach =
+
== Disadvantages of this approach ==
 
 
This approach has the following disadvantages
 
 
 
# Lets consider initialization - When we create <math>n</math> groups initially, we need to spend <math>O(n^2)</math> time to assign guarantees.
 
# Everytime a limit or a guarantee changes, we need to recalculate guarantees to ensure that the change will not break any guarantees
 
# The same thing as stated above, when a resource group is created or deleted
 
  
This can lead to some instability, a change in one group propagates to all other groups.
+
This approach has only one disadvantage: O(n) time needed to start a new container.

Latest revision as of 12:43, 23 May 2011


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 of how a guarantee can be provided:

  1. reserve desired amount in advance
  2. limit consumers to keep some amount free

The first way has the followong disadvantages:

Reservation is impossible for certain resources
such as CPU time, disk or network bandwidth and similar can not be just reserved as their amount instantly increases;
Reserved amount is essentially a limit, but much more strict
cutting off X megabytes from RAM implies that all the rest groups are limited in their RAM consumption;
Reservation reduces containers density
if one wants to run some identical containers, each requiring 100Mb on 1Gb system, reservations can be done for only 10 containers, and starting the 11th is 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;
        int i;

        if (N == 1) {
                l[0] = R;
                return;
        }

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

Disadvantages of this approach

This approach has only one disadvantage: O(n) time needed to start a new container.