Verified with 4.5.0-2601.

{

'snapshots': ['leto_ssd_450-2601-enterprise_28b_access'],

'metric': 'kv_max_ops_10M_reads_avg_ops_leto_ssd', 

'build_url': 'http://perf.jenkins.couchbase.com/job/leto/2793/',

'build': u'4.5.0-2601-enterprise',

'value': 832924.6

}

Will close the ticket when the same is verified in spock branch.

I am trying to repro in the daily sanity. With a standalone pillow fight command I see a 5-10% regression. When running with perfrunner I have tried:

• more or less threads - 10 to 100
• 1 to 10M items
• change the write percentage to 5%
• compaction threshold 30 to 100%
• 1 or 2 nodes
• the bucket is 1G and is about 10% of capacity
• generally I see CPU in the 90% range
• ops/sec in the the range of 200K to 800K
• 1 versus 2 node cluster

After all this experimentation I think (and I need to verify this) that a 1 node cluster is more like to uncover the regression than a 2 node cluster. Based on knowledge of the fix does this make sense? Of the above are there settings I should (or should not) change to help expose this?

I am trying to repro in the daily sanity. With a standalone pillow fight command I see a 5-10% regression.

... <cut> ...

After all this experimentation I think (and I need to verify this) that a 1 node cluster is more like to uncover the regression than a 2 node cluster. Based on knowledge of the fix does this make sense? Of the above are there settings I should (or should not) change to help expose this?

Your results approximately match mine - the figures I quoted in my local test (~23.5s -> 24.7s, or ~5%) were on a single Ubuntu 12.04 machine (24 logical CPU Sandybridge Xeon), running two nodes (via cluster_run). Interestingly I saw much more significant difference running the same pillowfight test on my OS X laptop (Haswell, 8 logical CPU) - where performance dropped by over 50%.

The underlying cause of the perf regression was lock contention on a per-bucket mutex, so having lots of different connections trying to concurrently access the same bucket would be expected to show the issue. I'd probably expect you'd see it sooner with smaller documents, lots of connections at the same time and mostly performing reads.

Also verified in 4.7.0-779.
The regression is fixed.