Need Out Of Order Execution to be enable-able for perf tests
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:
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.
Korrigan Clark June 25, 2020 at 8:04 PM
Ok sounds good, making it disable-able works just as well for testing purposes.
Matt Ingenthron June 25, 2020 at 6:43 PM
Can we enable this in 3.0.3 @Sergey Auseyau?
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.
Sergey Auseyau June 19, 2020 at 6:33 AM
Out of order is not enabled for libcouchbase yet
Fixed
Pinned fields
Click on the next to a field label to start pinning.
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()