UPCOMING WEBINAR: Cluster analysis: Classic, powerful, and still worth knowing When a document is busy in edit mode, a spinner appears to the right of the document name. If you click on the spinner you get an explanation of what the document is currently doing. In the example below, we can see that it's updating a variable called newCustomer.
Sometimes you will see a trash can next to a process. Clicking this will enable you to cancel the processing (though some processes cannot be canceled). For long-running drag and drop tables, you can also click on the Pause in the object inspector to pause the processing.
Documents will become busy when they are processing requests. Thus, if you click on a page that triggers lots of calculations, then move onto a new page before the first page has been calculated, and then click on another, and so on, Displayr will get slower and slower until it completes the calculations.
Similarly, if you have two people in a document in Edit mode at the same time, if one user does something resource-intensive (e.g., exports all the pages to PowerPoint, which requires every calculation to be updated), the other user will experience slowness.
In View mode, if you have a large number of users and they are doing more computationally expensive actions, such as filtering or using Explore mode, this will use up more resources and, at some point, will affect users. However, the effect of multiple users in View mode is relatively minor (having 50 or more users interacting at the same time should not be a problem).
Next
If the same process is running frequently or for a long time, you should consider some improvements to reduce processing time and reduce recalculations.