Running procs in VPS context :: possible to limit/throttle? [message #5163] |
Wed, 16 August 2006 10:15 ![Go to next message Go to next message](/theme/ovz3/images/down.png) |
HaroldB
Messages: 61 Registered: June 2006
|
Member |
|
|
Hello, the cpulimit resource does a fine job, but lets say a vps has 20 programs trying to run at once. They will use all of the cpulimit and beause they take longer to complete, the number of average running procs will be much higher than normal, which causes the hardware server's load to be higher.
So, it seems to me that cpulimit can hurt overal system performance under certain circumstances (more than a few concurrent, long-running processes per ve).
Is it possible to somehow limit the number of running procs in a ve? Am I missing something, like a simple workaround the problem stated above.
Thank you
Harold
|
|
|
|
|
|
|
|
|
|
|
Re: Running procs in VPS context :: possible to limit/throttle? [message #5205 is a reply to message #5197] |
Wed, 16 August 2006 16:19 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) ![Go to next message Go to next message](/theme/ovz3/images/down.png) |
HaroldB
Messages: 61 Registered: June 2006
|
Member |
|
|
Thanks for the info, that makes sense. Here is my question another way.
Lets say a ve runs a program like "cpu-burn" (program which uses all avaialble cpu cycles) once. If that process stays running, it would add a load of 1 to the hardware node because its exactly one running process. However, if that program is run 50 times concurrently, a load of 50 is added. All the while, the same amount of cpu time is used by the vps. maybe this is an inherent part of an operating system, I am not sure.
it seems like an easy way to DOS a openvz/vz hn, by running tons of procs in the vps, even though your cpu usage is the same. I have tested this on vmware and the hardware node feels no effect, because of the seperate schedulers I believe.
[Updated on: Wed, 16 August 2006 16:22] Report message to a moderator
|
|
|
|
|