MX7 uncommitted objects

0
Hi, We are upgrading to mx7 and noticed in the release notes that the uncommitted objects are handled differently and stored in the browser. We are experiencing a lot of slowness with this upgrade which we are assuming because of the uncommitted objects.  In the release notes, Mendix has this statement β€œTo keep the resource usage low, we periodically prune the stored state β€” we remove objects that are not displayed in the UI and not connected by references.” And my question is – how do you prune and can we invoke that ourselves on demand through a Microflow? The idea is to prune every time someone leaves the page by adding that process to the nav microflow.   I also saw other documentation stating a possible solution is to commit the uncommitted objects. We are experimenting with that. But main question is above.   Thanks
asked
0 answers