OpenVZ Forum


Home » General » Support » Handling resources for several VPS
Handling resources for several VPS [message #31811] Thu, 10 July 2008 09:38 Go to next message
beyondx is currently offline  beyondx
Messages: 21
Registered: October 2007
Junior Member
Hi everyone,

I´m just dealing with the UBC-values to find out the best performance setup for any VPS. First I used vzsplit to get a rough template, which was adapted to my needs. Due to the fact that I had to increases several barrier-values due to high-load peaks there´s one question I need to ask.
Is it possible to just say that the promised value is 10% of the HN and the max. is 95% for each VPS, so that in case of peaks the VPS just assumes as much resources as required? (I already noticed that there are no peaks for several machines at the same time)
I wonder whether I can do the following:
use vzsplit for 10 machines and for 1.
Then pick the max. values for the 10 machine config to use it for the barrier and pick the max value for the 1 machine config to use it for the maximum value.
I´m looking for an easy way since I need to do that for several HNs and dealing with each UBC-config might take a bunch of time.
Has anyone an idea?
I often experience that whenever a barrier is reached (e.g. kmemsize) some problems occur with running processes instead of just allocating more kmemsize-memory as the maximum-values permits.

Greetings

Norman
Re: Handling resources for several VPS [message #31860 is a reply to message #31811] Fri, 11 July 2008 11:04 Go to previous message
beyondx is currently offline  beyondx
Messages: 21
Registered: October 2007
Junior Member
Hi folks,

I just did a workaround by creating a resource template with vzspliz -n 1 which enanbles every machine to obtain almost all resources if necessary. Maybe not the most elegant way, but it works.

Greetings

Norman
Previous Topic: creating a centos-5 os-template...
Next Topic: vzdump sometimes failes --> vanished file
Goto Forum:
  


Current Time: Thu Jul 31 00:44:07 GMT 2025

Total time taken to generate the page: 0.20937 seconds