pprof analysis of where http://github.com/mongodb-labs/migration-verifier spends its time suggests roughly half of CPU time is spent in GC.

Pprof suggests that that’s because the driver allocates a new slice for each cursor response:

Can this be made to use memory pooling to reduce GC churn? Something like https://github.com/libp2p/go-buffer-pool might help.