I have a questions about the eviction in in-memory wiredTiger. After I insert enough data (by using mongo-perf) that overflow the cache size(256MB), the CPU usage always remains around 90%. After analysis, the thread of eviction server calls __evict_walk_tree because the data size is larger than the eviction trigger. However, there is no dirty page to be found and evict.