You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FWIW, one way to improve the perceived performance could be to prioritize searches around "known" locations of the tree.
I often open up a huge folder because I want the context, but in practice I spend 99% of my time in some tiny sub-tree. When I search for something, the thing I want is probably going to be "near" some of my currently open files. Perhaps sorting the search order to prioritize folders that are close to currently opened files would mean that all the matches show up instantly (and I don't really care that it keeps searching the rest of the folder for another 10s after I've found what I wanted).
Good point, it would prevent us from showing the results in a deterministic order because the order we search depends on what files are/were open. /cc @roblourens
Steps to Reproduce:
Searching for stuff is a key operation. It shouldn't be this slow.
The text was updated successfully, but these errors were encountered: