Closed GoogleCodeExporter closed 9 years ago
This is the way virtualization works. You can check the RAM using "top" or
"free -m" utilities inside container. You'll see the same numbers.
Free memory calculations are not so simple as it seems. If you see that 3.5Gb
out of 4Gb on physical machine, this doesn't mean you can allocate not more
than 500 Mb. Often free memory size is very small on active machine due to
cache usage. Memory allocated for buffers/cache can be freed if needed.
Anyway I'm not sure if it possible to change something here. Because in other
case free memory reported by "top", "free" or other tool inside container will
be different.
Original comment by sibprogrammer
on 9 Nov 2010 at 2:15
I know that "free" reports the same thing, but i figured it's better to have
something closer to the real value of the memory you can actually use.
If it's not possible to change it or it's too difficult, just leave it like it
is. It's a too small issue to worth all the troubles
Original comment by vlad.nedelcu
on 9 Nov 2010 at 2:21
Original comment by sibprogrammer
on 12 Nov 2010 at 4:39
Original issue reported on code.google.com by
vlad.nedelcu
on 9 Nov 2010 at 11:33