-
Type: Bug
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.6.0-rc4
-
Component/s: Networking
-
Labels:None
-
Service Arch
-
ALL
-
Reproduced on version r3.6.0-rc4-41-ge608b8b349.
On a two-shard environment, I generated a 100% query workload via the load.java attached (which is a modified version of load.java from SERVER-30613).
Configurations tested:
A. The sharded cluster operating with synchronous (default) service executor.
B. The sharded cluster operating with asynchronous (adaptive) service executor.
C. The sharded cluster operating with asynchronous (adaptive) service executor, except for mongos which was operating in synchronous mode.
Performance of A and C is comparable, whereas B shows 73% the query throughput of A.
For the test I used four AWS EC2 m4.4xlarge. One machine for the traffic generator, one for mongos and 1-member config server, and one machine for each shard (1-member replica set).
Attached logs and diagnostic data for the three configurations.