When doing high performance benchmark with a 2 shard cluster, throughput was 2.5x higher when using master/slave rather than replset.
This is obviously a huge performance degradation.
From profiling it seems due to the many calls to DBClientReplicaSet.getServerAddress() which take a lock.
By applying the tiny provided patch that caches the value, the issue goes away.