This is a check box option in System Settings, selecting the checkbox will enable the cache for records entered/updated in the application. User can view its changes and history in Cache Data under Maintenance.
Performance tuning and Optimization can be achieved using the caching mechanism. It is also helping keep CPU utilization low. This feature is based on the fact that the fastest and most efficient query possible is the one that you never execute against your SQL Server and it’s at the heart of caching – which its key is to enabling better application performance and increased scalability.
Illustration using an Example:-
Say if there are 100 items added into the application, when the ‘Use Cache’ is enabled then cache will record its entry as WORK_ITEM(History), Key and Version in the Cache List. So next time when same or other users access those items, it will be loaded from Cache thereby reducing the retrieval time for records and improving the performance.
Similarly if the user access the history of the work items then cache will record its entry too as WORK_ITEM(History), Key and Version in the Cache List. So next time when same or other users access the history for the items, it will be loaded from Cache thereby reducing the retrieval time and improving the performance. For each subsequent updates for any work item details, when user access the history the cache will be updated and so thereby improving the response time and performance.
- WORK_ITEM : The work item added/updated
- WORK_ITEM(History) : The work item History accessed and also after work item is updated
- Key : The work item id
- Version : The project Web version
It is most beneficial when there are thousands of records in an application, it will improve the application’s response time.