DocumentSourceCursor batch size was changed from 4MB to 16MB for MongoDB 3.4 as part of a broader effort to unify user request batch size at 16MB under SERVER-21797. This change led to a mongo-perf performance regression for the "Aggregation.skip" which appears as slower memcpy operations under VTune under DocumentSourceCursor::loadBatch and is likely due to the larger batches exceeding L2/L3 caches.

Testing across our aggregation micro-benchmarks shows a 4MB DocumentSourceCursor batch size restores previous performance across affected tests and does not penalize tests that may benefit from the batching behavior.