Changes to "Found" cache type in version 10.0.44

It seems that Microsoft will release a fix for a cache performance in version 10.0.44. (https://fix.lcs.dynamics.com/Issue/Details/?bugId=976894&dbType=3)

Based on the description of the fix, currently, any insert operation is flushing everything from the found cache, across all AOSes. When a record is inserted into another AOS, then the cache is flushed. In fact, it means that each AOS has to recache the data.

As far as I know, today any update/insert/delete triggers an update in SysCacheFlush, forcing other AOSes to flush whatever data they have cached. 

I guess, the fix is to stop flushing for inserts on Found cached tables. Therefore, an insert into a table where found data is cached will not require any cache invalidation (flushing).

I think, the fix can resolve the issue, when the data should be cached, but the kernel is performing queries towards the database, while the expectation is that the data should be fetched from cache. 

In addition, the fix can bring performance value, since there are some tables in the system that use the "found" cache type, which are used most often, for example - SalesTable, SalesLine, PurchTable, PurchLine.

My Performance Resource Page for Microsoft Dynamics AX 2012/Microsoft Dynamics 365 Finance and Operations

A performance issue can have many aspects, so in my opinion there is no universal advice. Below you can find the links I’ve collected, that I use for different cases as a starting point. 

If you face a system performance issue and you are not sure how to deal with it, I would recommend watching the TechTalk Performance Testing in Microsoft Dynamics 365 Series. In my opinion, it can be a good starting point in order to understand the process.

Also, I would recommend a training as another starting point so that you can have a knowledge about the tools: Work with performance and monitoring tools in Finance and Operations apps 

If you need to work with LCS environments:

• Monitoring and diagnostics tools in Lifecycle Services (LCS)
• Optimization advisor 
• How to analyze live performance issues with Dynamics 365 Finance and Operations

In some cases, a data clean-up operation can improve the system’s performance. For example, the “On-hand entries cleanup" operation can improve inventory operations performance. From the list, you can select the appropriate operations and repeat them regularly in order to keep the database size under control.

If the issue can be reproduced in the environment with installed Trace Parser, the links below can be useful as well:

• Take traces by using Trace parser
• Diagnose issues and analyze performance by using Trace parser

The following tips can help to improve the performance of a DMF project:

• 5 Tips to improve the performance in a DMF import project

If you would like to have a performance audit, Denis’ article will be really helpful:

• Dynamics AX performance audit 

If you use AX 2012 version the following links can be helpful:

• Performance Resource Page for Microsoft Dynamics AX 2012
• AX 2012 Performance 

Although the tips are for Ax 2012, some ideas from this page can be relevant for Dynamics 365 Finance and Supply Chain Management.