Home » Mailing lists » Users » how to get the current HN CPU utilization by particular CT
| how to get the current HN CPU utilization by particular CT [message #42699] |
Thu, 12 May 2011 14:19  |
knawnd
Messages: 27
Registered: April 2011
|
Junior Member |
|
|
Hi!
Sorry if that question has been already asked and answered before but I
couldn't found the reply.
I wonder what the proper way is to determine the current HN CPU
utilization by particular container? I need to know what percentage from
total hardware node CPU power a certain CT consumes. It is mentioned in
[1] the CPUUNITS and CPULIMIT parameters but as far as I understand
they are used to set some HN CPU usage limits (mini and max
I wonder If the following algorithm is the proper one.
1) If CPULIMIT is not set then a formula would be as below:
(CPUUNITS assigned to particular CT) x (summary of user and system CPU
consumption shown by top inside the CT) / (Power of the node" produced
by vzcpucheck).
For example,
ct_cpuunits=`vzcpucheck -v|grep 139`
ct_user_cpu=`vzctl exec 139 top -bn1|grep -i "cpu(s)"|cut -d: -f2|awk
{'print $1'}`|cut -d% -f1
ct_sys_cpu=`vzctl exec 139 top -bn1|grep -i "cpu(s)"|cut -d: -f2|awk
{'print $2'}`|cut -d% -f1
total_hw_cpu=`vzcpucheck |tail -1|cut -d: -f2|tr -d '[:space:]'`
ct_cpu_usage = $ct_cpuunits * ($ct_user_cpu+$ct_sys_cpu) / $total_hw_cpu
2) if CPULIMIT is set then
(CPULIMIT assigned to particular CT) x (summary of user and system CPU
consumption shown by top inside the CT)
Or there is a simpler way?
Thanks!
Nikolay.
[1] http://wiki.openvz.org/Resource_shortage#CPU
|
|
|
|
|
|
| Re: vzmigrate standby mode [message #42705 is a reply to message #42700] |
Fri, 13 May 2011 00:12  |
swindmill
Messages: 57
Registered: April 2007
|
Member |
|
|
I believe you can already do this with vzctl chkpnt and vzctl restore as
documented here:
http://wiki.openvz.org/Checkpointing_and_live_migration
On Thu, May 12, 2011 at 11:56 AM, Jean-Marc Pigeon <jmp@safe.ca> wrote:
> Hello,
>
>
> I think it will be very convenient to have a way to
> prepare/clone a VPS ready to start at moment notice
> (standby mode), a kind of action ready backup.
>
> I think the best way to do that is to modify
> vzmigrate to add "--standby", such the vzmigrate
> will work in --keep_dst mode and doing the --online
> mode but NOT stopping the VPS source and keeping the
> destination VPS in stop mode.
>
> Such starting vzmigrate --standby lets say
> once a day, could keep a fresh enough VPS
> ready to take action in case of major
> trouble on production HOST.
>
> Is there a better way to achieve this?,
> is vzmigrate the best candidate to do it?
> if so, I'll try to add "--standby" to
> vzmigrate.
>
>
>
> --
> A bientôt
> ============================================================ ==============
> Jean-Marc Pigeon Internet: jmp@safe.ca
> SAFE Inc. Phone: (514) 493-4280
> Fax: (514) 493-1946
> Clement, 'a kiss solution' to get rid of SPAM (at last)
> Clement' Home base <"http://www.clement.safe.ca">
> ============================================================ ==============
>
|
|
|
|
| Re: vzmigrate standby mode [message #42706 is a reply to message #42705] |
Fri, 13 May 2011 00:27 |
Jean-Marc Pigeon
Messages: 27
Registered: October 2007
|
Junior Member |
|
|
Hello,
On Thu, 2011-05-12 at 20:12 -0400, Sterling Windmill wrote:
> I believe you can already do this with vzctl chkpnt and vzctl restore
> as documented here:
Sure enough... and I'll be using it, but I want
a simple script to be able to be run via cron.
IMHO, vzmigrate is a good candidate to add
a "--standby" capability (trying to write something now).
>
>
> http://wiki.openvz.org/Checkpointing_and_live_migration
>
> On Thu, May 12, 2011 at 11:56 AM, Jean-Marc Pigeon <jmp@safe.ca>
> wrote:
> Hello,
>
>
> I think it will be very convenient to have a way to
> prepare/clone a VPS ready to start at moment notice
> (standby mode), a kind of action ready backup.
>
> I think the best way to do that is to modify
> vzmigrate to add "--standby", such the vzmigrate
> will work in --keep_dst mode and doing the --online
> mode but NOT stopping the VPS source and keeping the
> destination VPS in stop mode.
>
> Such starting vzmigrate --standby lets say
> once a day, could keep a fresh enough VPS
> ready to take action in case of major
> trouble on production HOST.
>
> Is there a better way to achieve this?,
> is vzmigrate the best candidate to do it?
> if so, I'll try to add "--standby" to
> vzmigrate.
>
>
>
> --
> A bientôt
> ============================================================ ==============
> Jean-Marc Pigeon Internet:
> jmp@safe.ca
> SAFE Inc. Phone:
> (514) 493-4280
> Fax: (514)
> 493-1946
> Clement, 'a kiss solution' to get rid of SPAM (at last)
> Clement' Home base <"http://www.clement.safe.ca">
> ============================================================ ==============
>
--
A bientôt
============================================================ ==============
Jean-Marc Pigeon Internet: jmp@safe.ca
SAFE Inc. Phone: (514) 493-4280
Fax: (514) 493-1946
Clement, 'a kiss solution' to get rid of SPAM (at last)
Clement' Home base <"http://www.clement.safe.ca">
============================================================ ==============
-
Attachment: smime.p7s
(Size: 3.83KB, Downloaded 462 times)
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Re: vzmigrate standby mode [message #42712 is a reply to message #42707] |
Fri, 13 May 2011 16:25 |
swindmill
Messages: 57
Registered: April 2007
|
Member |
|
|
The problem with the lsyncd approach is it doesn't guarantee filesystem
consistency. If you're running a database or any other application in the
container that has open file handles to data that is constantly being
manipulated, the data on the remote host isn't guaranteed to be consistent
at any point in time. Obviously this can be partially worked around by
creating application specific backups inside of the container using database
dump tools, etc.
vzctl chkpnt and restore guarantees consistency in that the state of the
container is dumped when the checkpoint is created and restored upon
restoration of said checkpoint. As long as the dump file and unadulterated
filesystem are available, restoration should result in a perfect copy of the
container as of when it was checkpointed. That being said, checkpointing
makes the container unavailable for a brief period of time and wouldn't be
ideal as a means of taking backups of production systems on a regular basis.
Checkpointing for this purpose would probably only make sense for a
container with data that doesn't change over time. A simple application
server that relies on an external database for instance.
lsyncd is interesting though, I haven't heard of it before and will
definitely be doing some research.
Best regards,
Sterling
On Fri, May 13, 2011 at 5:54 AM, Aleksandar Ivanisevic <
aleksandar@ivanisevic.de> wrote:
> Jean-Marc Pigeon <jmp@safe.ca> writes:
>
> > Hello,
> >
> >
> > I think it will be very convenient to have a way to
> > prepare/clone a VPS ready to start at moment notice
> > (standby mode), a kind of action ready backup.
>
> We do it with lsyncd http://code.google.com/p/lsyncd/ that allows only
> changed files to be rsynced. Put /vz/private/veidt and
> /etc/vz/conf/veid.conf in it and you are all set.
>
> Much easier on the machines, no cron necessary and the backups can be
> made really close to production.
>
> [...]
>
>
|
|
|
|
| Re: Re: vzmigrate standby mode [message #42714 is a reply to message #42712] |
Fri, 13 May 2011 18:28 |
Jean-Marc Pigeon
Messages: 27
Registered: October 2007
|
Junior Member |
|
|
On Fri, 2011-05-13 at 12:25 -0400, Sterling Windmill wrote:
> The problem with the lsyncd approach is it doesn't guarantee
> filesystem consistency. If you're running a database or any other
[...]
Agree with you, difficult to be an effective solution with
a real server running database, filesystem consistency
could be a real issue
> .
>
>
> vzctl chkpnt and restore guarantees consistency in that the state of
> the container is dumped when the checkpoint is created and restored
[...]
> period of time and wouldn't be ideal as a means of taking backups of
> production systems on a regular basis.
Using vzmigrate as starting point, I wrote a small
shell, with a small VPS (1.2 Gig Bytes) as test bench,
the preliminary result are (so fare) encouraging.
"standby" is done between 2 HOST on local network
Syncing private
Live migrating VPS...
Resuming local VPS
Times:
Second rsync: 0.507628 sec
Quota Generation: 0.00138903 sec
Suspended time: 0.631432 sec
Total time: 6.47325 sec
less than one second of suspend is good enough to me,
It is true the data-base within this test VPS
is not a very active one.
Keep in mind, there is many task (data dump transfer,
reload, ...) which can be done on the "standby"
VPS while the production one already resume task.
>
>
> Checkpointing for this purpose would probably only make sense for a
> container with data that doesn't change over time. A simple
> application server that relies on an external database for instance.
Agree with you.
Critical issue is the "suspend" time, if production
VPS is in very "volatile" data context, "suspend"
time could be a real issue.
>
>
> lsyncd is interesting though, I haven't heard of it before and will
> definitely be doing some research.
Agreed
>
>
> Best regards,
> Sterling
>
>
> On Fri, May 13, 2011 at 5:54 AM, Aleksandar Ivanisevic
> <aleksandar@ivanisevic.de> wrote:
> Jean-Marc Pigeon <jmp@safe.ca> writes:
>
> > Hello,
> >
> >
> > I think it will be very convenient to have a way to
> > prepare/clone a VPS ready to start at moment notice
> > (standby mode), a kind of action ready backup.
>
>
> We do it with lsyncd http://code.google.com/p/lsyncd/ that
> allows only
> changed files to be rsynced. Put /vz/private/veidt and
> /etc/vz/conf/veid.conf in it and you are all set.
>
> Much easier on the machines, no cron necessary and the backups
> can be
> made really close to production.
>
> [...]
>
>
>
--
A bientôt
============================================================ ==============
Jean-Marc Pigeon Internet: jmp@safe.ca
SAFE Inc. Phone: (514) 493-4280
Fax: (514) 493-1946
Clement, 'a kiss solution' to get rid of SPAM (at last)
Clement' Home base <"http://www.clement.safe.ca">
============================================================ ==============
-
Attachment: smime.p7s
(Size: 3.83KB, Downloaded 427 times)
|
|
|
|
|
|
| Re: Re: vzmigrate standby mode [message #42726 is a reply to message #42712] |
Mon, 16 May 2011 12:58 |
Jean-Marc Pigeon
Messages: 27
Registered: October 2007
|
Junior Member |
|
|
Hello,
Standby mode is working fine, I defined 2 scripts
"vzstandby" and "vzonair". I tested with one
VPS with a postgresql database application, sampling data
every minute and reporting via a web interface.
It is "funny" (but expected) to see last data
sampling vanishing from web page, when stopping
production VPS and "vzonair" backup VPS,
beside the system appearing just dropped in time,
everything seems to be working as usual.
The backup process suspend time was the most critical
to me. Test show, while the whole backup process can
be up to one minute long, the suspend time is less than
a second, which is quite acceptable.
vzstandby generate a standby VPS without quota, as
dumping quota seems to be "suspend time" expensive.
IMHO, to have a backup VPS working without quota
is not a real issue.
(quota can be restarted, when restarting the backup
VPS at a more convenient time).
I can provide vzstandby and vzonair to list if
some of us think it could be of interest.
(sure there is space for improvements...).
--
A bientôt
============================================================ ==============
Jean-Marc Pigeon Internet: jmp@safe.ca
SAFE Inc. Phone: (514) 493-4280
Fax: (514) 493-1946
Clement, 'a kiss solution' to get rid of SPAM (at last)
Clement' Home base <"http://www.clement.safe.ca">
============================================================ ==============
-
Attachment: smime.p7s
(Size: 3.83KB, Downloaded 468 times)
|
|
|
|
| Re: how to get the current HN CPU utilization by particular CT [message #42728 is a reply to message #42718] |
Mon, 16 May 2011 13:59 |
Tim Small
Messages: 24
Registered: April 2011
|
Junior Member |
|
|
On 14/05/11 09:27, knawnd@gmail.com wrote:
> As far as I understand in order to determine HN CPU load produced by
> certain CT it is enough to extract 'user', 'system' and 'uptime'
> values from /proc/vz/vestat twicely. Then the formula is
> ct_cpu_usage=100%*[(user_time_2 + system_time_2) - (user_time_1 +
> system_time_1)] / (uptime_2 - uptime_1)
Can't really remember I'm afraid, but that sounds plausible, I think the
figures collected from /proc are a total amount of CPU time used for
each container, so to determine usage, you have to take two readings and
divide by elapsed time. The figure you get is the total across all CPU
cores.
>
> The second question is if there are any plans to implement HN CPU load
> produced by particular CT in some of vz* tools (e.g. in vzcpucheck
> providing some additional option and print one more column required
> info about HN CPU utilization by each container)?
Dunno. Email the developers and see if they'd be willing to accept a
patch in principle?
If not (or in any case) - I wonder if a "dstat" plugin might be a good
solution?
Actually I just looked at the dstat man page, and there seems to be a
--vz-cpu option already....
Tim.
--
South East Open Source Solutions Limited
Registered in England and Wales with company number 06134732.
Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ
VAT number: 900 6633 53 http://seoss.co.uk/ +44-(0)1273-808309
|
|
|
|
|
|
|
|
| Re: Re: vzmigrate standby mode [message #42743 is a reply to message #42742] |
Wed, 18 May 2011 11:30 |
Tim Small
Messages: 24
Registered: April 2011
|
Junior Member |
|
|
On 18/05/11 11:54, Aleksandar Ivanisevic wrote:
> Sterling Windmill <sterling@ampx.net> writes:
>
> [...]
>
>
>> vzctl chkpnt and restore guarantees consistency in that the state of the
>> container is dumped when the checkpoint is created and restored upon
>> restoration of said checkpoint. As long as the dump file and unadulterated
>> filesystem are available, restoration should result in a perfect copy of the
>> container as of when it was checkpointed. That being said, checkpointing
>> makes the container unavailable for a brief period of time and wouldn't be
>> ideal as a means of taking backups of production systems on a
>> regular basis.
>>
> Yes, sorry, forgot to mention that. Unfortunately there is no easy
> solution for applications like databases that constantly change big
> files. You simply have to handle them separately, either by
> replication on a database level or by putting the disk in DRBD or SAN.
>
We use a hacked version of mylvmbackup to backup an entire container.
Each container lives on its own logical volume, and the process calls
into the logical volume to ask the database (mysql in this case) to make
its data-on-disk consistent. At this point, and LVM snapshot is taken,
then mysql is told it can carry on writing to disk. The LVM snapshot is
then fscked and mounted on a different mountpoint, once mounted, the
contents are rsynced to the standby machine, and the lvm snapshot is
removed.
I'm guessing that this could be combined with a vzctl chkpnt, but I
haven't looked into that.
Tim.
--
South East Open Source Solutions Limited
Registered in England and Wales with company number 06134732.
Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ
VAT number: 900 6633 53 http://seoss.co.uk/ +44-(0)1273-808309
|
|
|
|
| Re: Re: vzmigrate standby mode [message #42745 is a reply to message #42743] |
Wed, 18 May 2011 11:49 |
Tim Small
Messages: 24
Registered: April 2011
|
Junior Member |
|
|
On 18/05/11 12:30, Tim Small wrote:
>
> We use a hacked version of mylvmbackup to backup an entire container.
> Each container lives on its own logical volume, and the process calls
> into the logical volume to ask the database (mysql in this case) to make
> its data-on-disk consistent. At this point, and LVM snapshot is taken,
> then mysql is told it can carry on writing to disk. The LVM snapshot is
> then fscked and mounted on a different mountpoint, once mounted, the
> contents are rsynced to the standby machine, and the lvm snapshot is
> removed.
>
I should add that this is done at a relatively quiet time on the server
(if it's a server with lots of writes), as it has the side effect of
turning a single write on the containers storage into two writes and a
read (plus associated disk seeks) whilst the LVM snapshot exists.
Whilst the lvm snapshot is being created (< 1 second), writes to the
database block (reads continue as normal, however), then continue once
mysql gets the UNLOCK TABLES command. I don't know if there is
equivalent functionality available in other databases such as PostgreSQL
etc.
Cheers,
Tim.
--
South East Open Source Solutions Limited
Registered in England and Wales with company number 06134732.
Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ
VAT number: 900 6633 53 http://seoss.co.uk/ +44-(0)1273-808309
|
|
|
|
Goto Forum:
Current Time: Fri Oct 31 11:08:53 GMT 2025
Total time taken to generate the page: 0.12574 seconds
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
