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

[Doc]Good to add relevant useful stats on cbstats:timings and update sample output

    XMLWordPrintable

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • vulcan
    • cli, documentation
    • None

    Description

      Often customers want to know which cbstats-timing stats should they be looking at, typically to understand their get/set timings.

      The current documentation shows a generic output from timings, with no specific mention of these, which stats are most relevant https://developer.couchbase.com/documentation/server/current/cli/cbstats/cbstats-timing.html

      Imo, It would be good to include

      1. Which top stats to look for esp for gets and sets - 'get_cmd' and 'store_cmd'
      2. Update the sample  output to include 'get_cmd' and 'store_cmd'

        get_cmd (2 total)
          4us - 8us : ( 50.00%) 1 ####################################################
          1ms - 2ms : (100.00%) 1 ####################################################

       store_cmd (15767 total)
          2us - 4us     : (  0.72%)  114
          4us - 8us     : ( 29.99%) 4614 ############################
          8us - 16us    : ( 80.52%) 7967 #################################################
          16us - 32us   : ( 91.60%) 1747 ##########
          32us - 64us   : ( 97.77%)  973 #####
          64us - 128us  : ( 98.87%)  174 #
          128us - 256us : ( 99.25%)   59
          256us - 512us : ( 99.59%)   55
          512us - 1ms   : ( 99.81%)   34
          1ms - 2ms     : ( 99.94%)   21
          2ms - 4ms     : ( 99.97%)    5
          4ms - 8ms     : ( 99.98%)    1
          8ms - 16ms    : (100.00%)    3
          Avg           : (   15us)

       

      Attachments

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

        Activity

          For what it's worth cbstats timings is not what I would use to measure Couchbase Server performance.

          As the docs state:

          This only measures the time spent in the front-end thread for each operation, meaning that the timings may not be representative if items have to be fetched from disk as part of the operation.

          To retrieve more accurate timing statistics, use mctimings instead of timings.

          Here is the page for mctimings - Ketaki Gangal do you think additional info is required on the mctimings page?
          https://developer.couchbase.com/documentation/server/current/cli/mctimings.html

          matt.carabine Matt Carabine added a comment - For what it's worth cbstats timings is not what I would use to measure Couchbase Server performance. As the docs state: This only measures the time spent in the front-end thread for each operation, meaning that the timings may not be representative if items have to be fetched from disk as part of the operation. To retrieve more accurate timing statistics, use mctimings instead of timings. Here is the page for mctimings - Ketaki Gangal do you think additional info is required on the mctimings page? https://developer.couchbase.com/documentation/server/current/cli/mctimings.html

          Hi Matt, 

          Agree on the docs- to be fetched from disk - mctimings page has good information.

          But afaik, cbstats is widely used for timings information , esp non-disk based fetches; and imo it would be good to update this page with frequently used stats updates on the outputs.

           

          ketaki Ketaki Gangal (Inactive) added a comment - Hi Matt,  Agree on the docs- to be fetched from disk - mctimings page has good information. But afaik, cbstats is widely used for timings information , esp non-disk based fetches; and imo it would be good to update this page with frequently used stats updates on the outputs.  

          Ketaki Gangal my point wasn't really that it isn't used, it's that it probably shouldn't be used.

          I don't really use cbstats timings myself at all so it would be interesting to know which stats you feel are important for us to document (based on your experience of troubleshooting customer environments).

          Once we have those, we can work from there to improve this page.

          matt.carabine Matt Carabine added a comment - Ketaki Gangal my point wasn't really that it isn't used, it's that it probably shouldn't be used. I don't really use cbstats timings myself at all so it would be interesting to know which stats you feel are important for us to document (based on your experience of troubleshooting customer environments). Once we have those, we can work from there to improve this page.

          People

            simon.dew Simon Dew
            ketaki Ketaki Gangal (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty