On mongod, bulkWrite uses WorkingSet and QueuedDataStage to queue data and construct cursor response. Memory usage for WorkingSet and QueuedDataStage is unbounded. And they currently do not support spilling to disk. Additionally, we currently build the entire response in memory first without a limit.

This ticket is to limit the memory usage (e.g. capped at 100MB) for bulkWrite by putting a cap for the size of responses queued.

The end goal is to limit the memory usage when we build or cache responses for bulkWrite ops. Once this limit is hit, we should stop executing the remaining operations in this bulkWrite.