Unnecessary computations in the sync process #5217
Labels
awaiting-maintainer
Awaiting review from Bazel team on issues
topic: sync
Issues related to the sync operation
type: bug
The issue will outline a few low hanging fruits in the sync process that can help optimizing the incremental sync times in the plugin.
WorkingSet
computation can be skipped if expand to working set is disabled, computed 3 times per incremental sync.Avoiding this computation can reduce sync times by roughly 3x git diff durations.
BazelInfo
is computed 5 times during a incremental sync, with no caching involved.Avoiding this computation can reduce sync times by roughly 5x bazel info durations.
For the Bazel info case, the idea is to cache the result and invalidate once needed, for example in a bazel sync error, alternatively, if that would be too tricky or error prone, we can proceed with computing it only once per sync.
The text was updated successfully, but these errors were encountered: