Uploaded image for project: 'Couchbase Server'
  1. Couchbase Server
  2. MB-48857

Magma YCSB Workload B has higher 99th percentile latency on build 7.1.0-1456

    XMLWordPrintable

Details

    • Untriaged
    • 1
    • Unknown

    Description

      99th Percentile READ Latency(ms), Workload B, 3 nodes, 1 bucket x 1.5B x 1KB, Uniform distribution, 15K ops/sec, 1% Resident Ratio, Magma

      99th Percentile UPDATE Latency(ms), Workload B, 3 nodes, 1 bucket x 1.5B x 1KB, Uniform distribution, 15K ops/sec, 1% Resident Ratio, Magma

      Attachments

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

        Activity

          sarath Sarath Lakshman added a comment - - edited

          Between 1430 and 1431, the latency has increased.

          The only changes for kv-engine and magma are as follows. They do not seem to be the cause for latency increase.

          CHANGELOG for kv_engine:
          * Commit: a3416c22c1d5f53c80d512204c05d5a099c14606 in build: couchbase-server-7.1.0-1431
          MB-48096: Optimise markLegacyDiskSnapshot() to reduce scanning time[2/2]
           
          CHANGELOG for magma:
          * Commit: 7811d977a29f2fff302cd6733279627b06ec05b6 in build: couchbase-server-7.1.0-1431
          MB-48533 stats: Fix population of get stats counters
          
          

          sarath Sarath Lakshman added a comment - - edited Between 1430 and 1431, the latency has increased. The only changes for kv-engine and magma are as follows. They do not seem to be the cause for latency increase. CHANGELOG for kv_engine: * Commit: a3416c22c1d5f53c80d512204c05d5a099c14606 in build: couchbase-server-7.1.0-1431 MB-48096: Optimise markLegacyDiskSnapshot() to reduce scanning time[2/2]   CHANGELOG for magma: * Commit: 7811d977a29f2fff302cd6733279627b06ec05b6 in build: couchbase-server-7.1.0-1431 MB-48533 stats: Fix population of get stats counters

          The latest build 1504 has the latency numbers back to normal. I do not know the cause and effect. The code changes between the original regressed builds does not have seem to be the cause. Potentially some environment-related problem. Closing the issue as the numbers are back to normal.

          sarath Sarath Lakshman added a comment - The latest build 1504 has the latency numbers back to normal. I do not know the cause and effect. The code changes between the original regressed builds does not have seem to be the cause. Potentially some environment-related problem. Closing the issue as the numbers are back to normal.

          People

            sarath Sarath Lakshman
            bo-chun.wang Bo-Chun Wang
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty