Project: aptanastudio
Issue APSTUD-4301: Reduce number of refreshes in Git Index and reduce work done during refresh
Previously I thought we could entirely remove refreshes when files change inside a git connected project. Turns out that we couldn't but there are other things we can do: - When we get resource change events, only update the changed files, don't do a full batch refresh. - Don't call batch refreshes from some actions like deleting files/folder or moving files through our UI. The connected filewatcher on the repo should pick up a file event or two to the "index" file which will trigger a batch refresh. - When we do refresh we call one process and then we spawn off 3 parallel jobs to each run another process to update our listings. We may be able to reduce the number of processes down to as low as one in most cases (or two in worst case).
Story points: 8