We have been having some issues finding and queueing pages in the cache that help meet the updates target, especially in cases where the cache is very large.

I noticed that the eviction server uses page->modify != NULL as a proxy for a page contributing to the updates content in cache. That isn't always the case, there are two notable exceptions:

• Internal pages
• Pages associated with trees that are configured to be in-memory

I suggest that we abstract out the check as to whether a page is a candidate to meet the updates threshold, so we can consistently check a (slightly) broader set of criteria.