Uploaded image for project: 'Product Technical Learning'
  1. Product Technical Learning
  2. PTL-8168

RH442-123: Chapter 12 Section 7: Overcommitting Memory - Typo in Documentation

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • RH442 - RHEL 8 1 20190828
    • RH442 - RHEL 7 2 20150420
    • RH442
    • None
    • 12
    • en-US (English)

      URL:
      Reporter RHNID:
      Section: -
      Language: en-US (English)|
      Workaround:

      Description: Student Guide states that 0.5 seconds is 500 centisecs when it is actually 50 centisecs .
      ----------------------------------------------------------------------------------------------
      When using a database server workload, an administrator may make the following type of adjustment: vm.dirty_background_ratio=3, vm.dirty_ratio=80, vm.dirty_expire_centisecs=500, and vm.dirty_writeback_centisecs=100. With this configuration, the machine will start writing out dirty pages from cache if they are over 3% of system memory, but will not force writes until dirty pages are over 80% of system memory. Every one-tenth of a second (100 centiseconds), the system will check to see if pages have expired and need to be flushed to the I/O subsystem. Lastly, pages expire from cache after .5 seconds (500 centiseconds). Using this configuration, pages expire from cache more quickly, but the kernel will continue to do background writes of the dirty pages unless they are consuming a ridiculous amount of system memory.
      ----------------------------------------------------------------------------------------------

              rht-hquatrem Herve Quatremain
              amadhusu Achyut Madhusudan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: