mdzidic / ovz-web-panel

Automatically exported from code.google.com/p/ovz-web-panel
Other
0 stars 0 forks source link

memory display error #375

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Steps to reproduce:
1. login to host server
2. start comnmand top
3. listing memory

Actual result: 16gb

Expected result: mysql prozesses was killed

Version of the product: newest

Server OS: debian squeeze 64 bit

Browser: newest ie/ff

Additional information:
if i login to ssh memory was full and in ovz panel memy is used only 4% of 
memory

whats here wrong? if i have a host with 8 GB memory and i add 4x 2gb vm memory 
in ssh is full and in ovz panel 3% used. do ovz used all assigned memory?

well if i do assigned memory in this exsample, hsot maschine killed prozesses 
of vm´s.

please help. thanks

Original issue reported on code.google.com by cod...@iscgr.de on 25 Nov 2011 at 10:53

GoogleCodeExporter commented 9 years ago
Hello. Please provide the result of `vmstat -s` command when you say memory is 
full.

Original comment by threed...@gmail.com on 2 Dec 2011 at 2:55

GoogleCodeExporter commented 9 years ago
vmstat -s
     16440984 K total memory
     16222800 K used memory
      6996268 K active memory
      8098944 K inactive memory
       218184 K free memory
       550272 K buffer memory
     12280564 K swap cache
     16013828 K total swap
         1624 K used swap
     16012204 K free swap
      5570257 non-nice user cpu ticks
          374 nice user cpu ticks
      2726625 system cpu ticks
    365682194 idle cpu ticks
       602271 IO-wait cpu ticks
        30838 IRQ cpu ticks
       188447 softirq cpu ticks
            0 stolen cpu ticks
     22485181 pages paged in
    504843600 pages paged out
            0 pages swapped in
          406 pages swapped out
    506340305 interrupts
    709885198 CPU context switches
   1322349668 boot time
      1958800 forks

Original comment by cod...@iscgr.de on 2 Dec 2011 at 8:47

GoogleCodeExporter commented 9 years ago
Panel shouldn't eat a lot of RAM. I tried to explain regular values in 
http://code.google.com/p/ovz-web-panel/issues/detail?id=240
Maybe you're checking free memory using "free -m" command and afraid of small 
amount of free memory. There should be almost no free memory on active linux 
box. Most of the memory should be allocated by active processes or buffers 
(that allows to start processes again more quickly).

Original comment by sibprogrammer on 5 Dec 2011 at 3:36