ITER-FLUSH-AFTER" class="id_link">#</a></dt><dd><p>
         Whenever more than this amount of data has
         been written by the background writer, attempt to force the OS to issue these
         writes to the underlying storage.  Doing so will limit the amount of
         dirty data in the kernel's page cache, reducing the likelihood of
         stalls when an <code class="function">fsync</code> is issued at the end of a checkpoint, or when
         the OS writes data back in larger batches in the back