Uploaded image for project: 'Couchbase C client library libcouchbase'
  1. Couchbase C client library libcouchbase
  2. CCBC-1265

Need Out Of Order Execution to be enable-able for perf tests

    XMLWordPrintable

Details

    Description

      I need some way to enable out of order execution for pillowfight and python sdk based tests. Both these tests categories require LCB to enable out of order execution first as they both depend on LCB. Ideally it would be a simple switch and not require re-compilation... something like this for pillowfight:

      cbc-pillowfight -U couchbase://cb-example-0000.cb-example.default.svc/default -I 10000 -B 1000 -c -1 -r 50 -t 1 -u Administrator -P password -OoO True

      And something like this for python sdk:

      collection = bucket.scope('scope-1').collection('collection-1')

      collection.enable_ooo()

       

      Attachments

        Issue Links

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

          Activity

            korrigan.clark Korrigan Clark added a comment - Ellis Breen

            Note that our plan is to enable OoO by default on all releases. This may already be done even in 3.0.2, but not sure without checking. The reason for this is that it'll only be negotiated on in releases that have it.

            ingenthr Matt Ingenthron added a comment - Note that our plan is to enable OoO by default on all releases. This may already be done even in 3.0.2, but not sure without checking. The reason for this is that it'll only be negotiated on in releases that have it.

            Out of order is not enabled for libcouchbase yet

            avsej Sergey Avseyev added a comment - Out of order is not enabled for libcouchbase yet

            Can we enable this in 3.0.3 Sergey Avseyev?

            Also, Korrigan Clark, it won't have the "true" as you outline as the plan of record is to enable it by default. There should be a method of disabling it though for the A/B test you're indicating. Client wil; HELO negotiate for it, cluster will enable it if available. You should be able to see what's negotiated via logging.

            ingenthr Matt Ingenthron added a comment - Can we enable this in 3.0.3 Sergey Avseyev ? Also, Korrigan Clark , it won't have the "true" as you outline as the plan of record is to enable it by default. There should be a method of disabling it though for the A/B test you're indicating. Client wil; HELO negotiate for it, cluster will enable it if available. You should be able to see what's negotiated via logging.

            Ok sounds good, making it disable-able works just as well for testing purposes.

            korrigan.clark Korrigan Clark added a comment - Ok sounds good, making it disable-able works just as well for testing purposes.

            In 3.0.3 it will be enabled by default, but to disable sending it in HELLO handshake, pass enable_unordered_execution=false in connection string.

            avsej Sergey Avseyev added a comment - In 3.0.3 it will be enabled by default, but to disable sending it in HELLO handshake, pass enable_unordered_execution=false in connection string.

            Build couchbase-server-7.0.0-3115 contains libcouchbase commit cbe1aa0 with commit message:
            CCBC-1265: enable out of order execution by default

            build-team Couchbase Build Team added a comment - Build couchbase-server-7.0.0-3115 contains libcouchbase commit cbe1aa0 with commit message: CCBC-1265 : enable out of order execution by default

            People

              avsej Sergey Avseyev
              korrigan.clark Korrigan Clark
              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