> ... > For implementing guarantees, we can use limits. Please see > http://wiki.openvz.org/Containers/Guarantees_for_resources.
Nack. This seems to be correct for resources like cpu, disk or network bandwidth but not for the memory just because nobody in this wiki speaks about the kswapd and page reclaim (but it's true that a such demon does not exist for cpu, disk or... then the problem is more simple). For a customer the main reason to use guarantee is to be sure that some pages of a job remain in memory when the system is low on free memory. This should be true even for a job in group/container A with a smooth activity compared to a group/container B with a set of jobs using memory more agressively... What happens if we use limits to implement guarantees ? >> ... >> The idea of getting a guarantee is simple: >> if any group gi requires a Gi units of resource from R units available >> then limiting all the rest groups with R - Gi units provides a desired >> guarantee If the limit is a "hard limit" then we have implemented reservation and this is too strict. If the limit is a "soft limit" then group/container B is autorized to use more than the limit and nothing is guaranteed for group/container A... Patrick ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ ckrm-tech mailing list https://lists.sourceforge.net/lists/listinfo/ckrm-tech