Back off on calls for new notes in issues and MRs
Problem to solve
When reviewing issues I sometimes have 10-20 issues open at the same time. The more issues that are open the more things start to slow down due to the constant calls for updates on each open tab. This is especially noticeable on a slow connection (when tethering to mobile, etc)
This affects calls to gather quick actions, labels and user autocomplete calls as well as the actual submission of a comment
- Should these calls back off if they are timing out?
- Should these calls be made if the tab is not active?
Further details
Calls to /:project/issues/:iid/realtime_changes
every few seconds on a large number of open issues will quickly saturate a slow connection
Proposal
Back off exponentially if requests are failing or stop requests if the tab is inactive?
What does success look like, and how can we measure that?
Less degradation of experience when opening multiple GitLab tabs for issues and Merge Requests