When you edit an output on a page (e.g., a calculation or a table), Displayr will automatically update any dependent calculations on the same page. This uses up Displayr resources and can cause slowness. This can be avoided by:
Turning off automatic updating
Consider the dependency graph below. If everything in the dependency graph is on the same page, and a user edits calc.7 this will cause the other nine outputs on the page - the three calculations and six visualizations - to automatically update.
If Calculate automatically is unchecked for calc.4, calc.5, and calc.6, this will prevent any calculations from being updated when calc.7 is edited.
A risk with this strategy is that you may forget to turn the calculations back on.
Editing the calculation on a different page
By moving calc.7 to a different page (which can be done by just dragging it onto a different page in the Report tree), we ensure that when we edit calc.7 the other outputs will not automatically update (they will only update when the user is on the page that they are located).
Once the editing is finished, the output can be moved back to its original place.