This is not regarding any requirement. Here is what I wish to know.
I am a D365FO developer. Often I work with financial postings. I notice one thing while developing. When I build my project and then load the instance, the very first financial posting takes a lot of time. But after the first posting, all the posting's execution time is been boosted tremendously. I was just curious about this and tried to find whether Microsoft has did something in development front to achieve this or is this nor related to any development. This is not related to any requirement. I am just curious to know and if there is some development done by Micrsoft for this I would like to learn and try it out with my developments.
Is there any optimization did by Microsoft to increase the speed of financial postings
Hi Andre,
Thanks for your response.
So as a developer the only thing that I have control over is, just the table cache and global cache. Every other optimization will be done by the system itself on the second run. But, will table caching provide reasonable optimization to the performance? Or is it something just like unnoticeable to the user?
I am just trying to understand practically in which scenario table cache will be beneficial to the user interface.
Is there any optimization did by Microsoft to increase the speed of financial postings
Hi John,
The behavior you described has to do with caching of data and objects. The first time, it is building up cache. After the first run, retrieving objects and data from memory is a lot quicker.
You will experience the same by default with your coding. E.g. the fist time a (larger) form will be opened, it is also slower than the consecutive times. You can manage some caching on table objects, or set some variables in a global cache. Table caching only makes sense in case it is not a transaction table and data is not updated frequently.
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.