This task aims to understand something that has been observed more and more lately that is a problem: the maximum page size seen when being evicted.

By stressing a page with many updates, we would make the page grow more and more which should be ultimately evicted. The size of the page when being evicted is tracked by the metric "ss wt cache maximum page size at eviction". We have seen in the field that this can go up to hundreds of MB which is unexpected and much more than the expected value (< 10 MB).

The test should reproduce the problem and eventually expose the root cause. The cppsuite could be used for this purpose.

Now the problem could be reproduced easily, see this comment for the next steps. TLDR; create a test to assess the r/w latency while stressing the maximum page size at eviction.