This ticket is to add write state tracking to the current read state tracking used for writeahead.  It is called "writeahead state tracking", and attempts to predict future writes based on past writes.  Because it does not need to deal with a variable size window (where we sometimes read part of the window due to readahead limits), it can be massively simpler than the readahead code.

The eventual goal of this is to recognize strided patterns, and in combination with the server reporting lock contention back to the client, do automatic lockahead.

This is also being done to help start a conversation while we (mostly wshilong  ) are considering how to update/improve the readahead code.  It maybe possible to share some code, or at least an approach.