We are trying to upgrade a replica set with many collections and indexes to WiredTiger. The replica set has 30k collections and 14 indexes per collection.

The initial data sync and index build works fine but the server makes very little progress once it starts to apply the replication log. It seems to make no progress for ~15 minutes during this time it consumes a full core of CPU and does very little I/O. It will does a burst of I/O for a minute or so before falling back to consuming a lot of CPU.

Based on the attached perf profile it looks like most of the CPU is being consumed by the eviction thread. (Possibly during a checkpoint?)

Let me know if there is any additional information I can provide to help track this down.