Table data cache method (Entire table, Found, FoundAndEmpty, NotInTTS, etc.) is since the beginning of the history one of the topics that are getting hit in almost every performance review. The reason for it, is that different businesses and customers are using the application in different context.

Currently the data cache method is a part of AOT table properties that is even not accessible by the table extensions. The better situation would be that we make this configurable. i.e. whenever there is a user override value available in the configuration that the AOS is using that value from the configuration and otherwise from the AOT property.