As others have written, the 10.0.44 preview is now made available, and it gives a glimpse of what is to come in June. A lot have already been shared in blogs and LinkedIn feeds. But I like to go deeper, and this time I found a jewel that I think will have a noticeable performance impact. See https://fix.lcs.dynamics.com/Issue/Details/?bugId=976894&dbType=3

What is issue are explaining is that when a record is inserted on another AOS, then the cache is flushed on the table in question. In essence, this means that each AOS have to recache the data. Two tables that are quite recognizable that have Cache Lookup = found is SalesTable and SalesLine.

So one of the issue I have seen, when looking for performance, is that data that should be cached, the kernel are performing queries towards the DB, while the expectation is that the data should be fetched from cache.

I don’t have any clear measurements on what the actual impact will be, but I know for sure that caching is one of the main mechanisms for improved performance and user experience.

Good catch Microsoft! We need more of these generic performance improvements.