Uploaded image for project: 'Couchbase Documentation'
  1. Couchbase Documentation
  2. DOC-9868

Should suggest using Disk I/O Optimized mode for Magma

    XMLWordPrintable

Details

    • Task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • Neo
    • Neo.M1
    • core-server
    • None
    • 1

    Description

      This affects two pages:

      For the first page (Threading discussion in Storage Settings):

      Current para is:

      A high thread-allocation may improve performance on systems whose hardware-resources are commensurately supportive (for example, where the number of CPU cores is high). In particular, a high number of writer threads on such systems may significantly optimize the performance of durable writes: see Durability, for information.

      Lets add the following sentences at end of above para:

      A high number of reader and writer threads will benefit disk based workloads that require high throughput especially when using high end disk drives such as NVMe SSDs. This is likely to be the case when using Magma as the storage engine. In this case it is best to choose 'Disk i/o optimized' mode for Reader and Writer thread settings.

      It will be good to link to the Data Settings from the mention of 'Disk i/o optimized'

      For the second page (Data settings section in  General Settings page):

      Add the following sentence here as well:

      A high number of reader and writer threads will benefit disk based workloads that require high throughput especially when using high end disk drives such as NVMe SSDs. This is likely to be the case when using Magma as the storage engine. In this case it is best to choose 'Disk i/o optimized' mode for Reader and Writer thread settings.

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          shivani.gupta Shivani Gupta added a comment - Sarath Lakshman Srinath Duvuru John Liang   FYI
          simon.dew Simon Dew added a comment -

          Moving this ticket to Neo milestone 1 as it came in after the scope was agreed. To do after internal GA.

          simon.dew Simon Dew added a comment - Moving this ticket to Neo milestone 1 as it came in after the scope was agreed. To do after internal GA.

          People

            simon.dew Simon Dew
            shivani.gupta Shivani Gupta
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty