OpenVZ Forum


Home » Mailing lists » Users » occasional high loadavg without any noticeable cpu/memory/io load
RE: occasional high loadavg without any noticeable cpu/memory/io load [message #46462 is a reply to message #46459] Tue, 22 May 2012 12:54 Go to previous messageGo to previous message
Esm is currently offline  Esm
Messages: 15
Registered: August 2011
Junior Member
You could check your <VEID>.conf with vzcfgvalidate. But I think there is
quite a risk when giving one of your CT’s unlimited resources. If you want
to read-out the UBC’s from the node and see when one fails I could recommend
you a very good script I’m using myself;
http://wiki.openvz.org/UBC_failcnt_reset There is no need to reset the
value’s inside your CT.





Van: users-bounces@openvz.org [mailto:users-bounces@openvz.org] Namens Rene
C.
Verzonden: dinsdag 22 mei 2012 14:17
Aan: users@openvz.org
Onderwerp: Re: [Users] occasional high loadavg without any noticeable
cpu/memory/io load





On Tue, May 22, 2012 at 6:59 PM, Esmé de Wolf <esme@elements.nl> wrote:

I also think that these UBC settings are not consistent. Especially when you
have all containers configured with these same UBC settings you will have
soon or later problems.



See: http://wiki.openvz.org/UBC_consistency_check and other pages on the
WIKI.



Kind Regards,


Esme



I read that UBC page already and used it to set these values.



No, all my containers do not have the same UBC settings, they were set
depending on how much resources each container should have.



Please let me know where any of the values in my conf file conflicts with
the UBC recommendations.


I do understand that they may need to be fine tuned in each case, but that's
basically what this question is about :)



So basically at this time I have two questions I don't understand:



1) how is it possible to have physpages hit the limit when top never shows
more than about 75-80% of the memory used?

2) how did dcachesize hit limit when both df -i and df -h shows plenty of
resources - and haven't been close to limits?



Could the values in the beancounter file be old? Is there a way to reset
them (without restarting the CT) ?



Best,

Rene

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: cat: /proc/self/mountinfo: Cannot allocate memory
Next Topic: vmstat and floating point exception
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Wed Dec 17 18:04:26 GMT 2025

Total time taken to generate the page: 0.74832 seconds
Powered by FUDforum Powered by Virtuozzo Containers