Is this the scenario you are talking about: User A initiates a refresh of a large view, and Users B and C are then unable to access any other view in the application assuming that they already are in the application, or are unable to open the application
while a refresh or rebuild of the large view is taking place? If so, does the server go to high CPU when the view is being updated?