Degradation of Instance Performance due to viewrule_all_cache after upgrading to Washington DC releaseDescriptionServiceNow has identified an issue in the Washington DC release where the 'viewrule_all_cache' can consume excessive memory, resulting in memory contention, increased garbage collection and performance degradation. This cache was added in the Washington DC release to improve the performance in loading of forms in Workspaces. Instances that do not use workspaces much are not affected by this issue.Steps to Reproduce Due to the nature of this issue, it is not easy to reproduce.WorkaroundServiceNow is actively working on providing a permanent fix. But in the meanwhile as a workaround, a system property with name 'glide.ui.view_fetcher.cache' can be added and set its value to false. This will disable this cache. After setting this property, a cache flush needs to be performed and restart any nodes if required. After upgrading to a fixed version, we recommend enabling this cache again by either setting the 'glide.ui.view_fetcher.cache' system property to true or by deleting this system property. This ensures you get the performance improvements in loading of the forms in Workspaces. Note: Please confirm with the ServiceNow Customer Support team before correlating performance issues with this defect and applying this workaround. Related Problem: PRB1783850