| |||||||||||||
Idle and stale page trackingIdle and stale page trackingPosted Oct 7, 2011 20:45 UTC (Fri) by giraffedata (subscriber, #1954)Parent article: Idle and stale page tracking Why does Google partition the memory? If they're just going to move memory from partition to partition to make the utilization even, that seems to take back one of the typical benefits of partitioning memory.
(Log in to post comments)
Idle and stale page tracking Posted Oct 9, 2011 21:22 UTC (Sun) by sethml (subscriber, #8471) [Link]
Because they have another option: move a process to another machine. Imagine you start a batch job that requires 10,000 processes. Some of your processes may get dumped on machines running web search. Now imagine one of those search processes gets a bunch of requests and its working set increases - your process may get killed to avoid making web search thrash. The controller for your job can then move that process's work somewhere else. This lets Google take advantage of underused resources on production clusters without disrupting production services.
|
|||||||||||||