[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-devel] How does the self-ballooning daemon calculate the selftarget?
Hi Jia
--
First,
please note that when XENBALLOON_MINMEM is set to 0, that does NOT mean
0MB. As described in the text in the xenballoon config
file, XENBALLOON_MINMEM==0 means that the heuristic is used which is in my
previous reply.
As for Committed_AS, it is certainly not a perfect metric. It was just an adequate one (and much better than no metric at all). I'm not sure, but your observation of meminfo not being periodically updated may be a result of a balloon driver bug that was fixed in a patch by Ian Campbell here: If you
are interested in the area of memory utilization optimization, I'd encourage you
to try tmem, which is in xen-unstable and the Oracle VM 2.2 product. (See
http://oss.oracle.com/projects/tmem
for more info.)
Dan
P.S.
The minimum memory heuristic patch for the balloon driver is
here:
_______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |