anchor.diff:  * **`mlockall`**
   +
   --
  -The third option on Linux/Unix systems only, is to use
  -http://opengroup.org/onlinepubs/007908799/xsh/mlockall.html[mlockall] to
  +The third option is to use
  +http://opengroup.org/onlinepubs/007908799/xsh/mlockall.html[mlockall] on Linux/Unix systems, or https://msdn.microsoft.com/en-us/library/windows/desktop/aa366895%28v=vs.85%29.aspx[VirtualLock] on Windows, to
   try to lock the process address space into RAM, preventing any Elasticsearch
   memory from being swapped out.  This can be done, by adding this line
   to the `config/elasticsearch.yml` file:
  
positive.code: [[setup-configuration-memory]]
  ==== Memory Settings
  
  The Linux kernel tries to use as much memory as possible for file system
  caches and eagerly swaps out unused application memory, possibly resulting
  in the elasticsearch process being swapped. Swapping is very bad for
  performance and for node stability, so it should be avoided at all costs.
  
  
negative.code: The simplest option is to completely disable swap. Usually Elasticsearch
  is the only service running on a box, and its memory usage is controlled
  by the `ES_HEAP_SIZE` environment variable.  There should be no need
  to have swap enabled.
  
  On Linux systems, you can disable swap temporarily
  by running: `sudo swapoff -a`. To disable it permanently, you will need
  to edit the `/etc/fstab` file and comment out any lines that contain the
  word `swap`.
  
  On Windows, the equivalent can be achieved by disabling the paging file entirely
  via `System Properties → Advanced → Performance → Advanced → Virtual memory`.
  
  --
  
  * **Configure `swappiness`**
  