Andy suggested "large" = 250,000 chunks. There doesn't need to be much (if any) data in the sharded collection itself. The purpose is to stress how the resharding coordinator behaves during the multi-document transaction to insert all the config.chunks documents in kInitializing and to update all the config.chunks documents in kDecisionPersisted (commit).