At the moment we let update chains grow arbitrarily long - limiting their length only by considering the total page memory footprint. Having long update chains can lead to performance issues, as traversing them is slow and happens while serializing access to a page.

We could consider queuing any page with an excessively long update chain for forced eviction - similarly to how we force evict pages with lots of deleted refs.