Per request from the Support team (Case#02157929), I am creating this urgent feature request.
The customer(s) are severely impacted by the continuous memory consumption when the open template (a dashboard) has automatic refresh every n minutes. At a certain customer, memory usage increased from 4GB to 64GB due to refreshes...
We suspect this is a result of undo/redo functionality. If you agree, then we need:
* Ability to set the maximum number of possible undo/redo with '0' as a valid value which means no undo/redo. This should be a configuration variable at application and document levels, with an API to set it.
* Add an API to force flush the reserved memory for redo/undo. This would be useful if the user wants to flush the undostack every n number of refreshes...
Please plan to implement this ASAP.
Thanks.
For use cases where data needs to be refreshed regularly, we recommend using the Scheduled Updates feature.