| Re: VE memory misconfigured / misreported [message #32648 is a reply to message #32647] |
Thu, 21 August 2008 16:36   |
piavlo
Messages: 159
Registered: January 2007
|
Senior Member |
|
|
| csigman wrote on Thu, 21 August 2008 19:11 |
So, I guess the problem is that the swap and actual ram are shared from the ve's perspective, and java apps might allocate a huge amount of ram, but generally this is mostly in swap.
|
Apps allocate vitrual memory which is neither in ram nor is swap. Only the real used memory is in ram or swap, and VE does not know where it is (it only sees "virtual" ram), but this does not matter.
| Quote: |
I've toned down the memory usage of some of the java parts and that makes it so that it's using a lot less, but still not the most ideal setup. Luckily this is development, and production isn't in a VE.
|
I think you are missing the point, the app virtual memory allocation does not depend if you are using OpenVZ or Vanilla kernel. Currently your VE is using 171M from RAM+SWAP
on HN or equally 171M of "virtual" ram on VE, so it is still safe for production.
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
