Slow startup for large projects

[antelle]

Each time you open a project and bring up fuzzy-finder, it shows 'Indexing...' for several seconds. For large projects it's quite annoying.
Suggested solution: save per-project caches after reindex and load them on startup, delete old caches. I've implemented it in my fork here and can make a pull request, if this idea is welcome.
On my project with ≈50k files, fuzzy finder can be used immediately after startup and it saves time.

[winstliu]

It definitely seems feasible. A PR would be nice, though I can't guarantee that we'll end up going with that solution in the end.

[eeejay]

I hack on the Gecko, and there are almost 200k files in the source tree. It takes fuzzy finder 17 seconds to index the project. That would be bad enough if it did it the first time you opened it, but it also does it every time you use the finder after refocusing the window.

I made a few changes (pull #301) to optimize how the project gets indexed. There is a 40x speedup, now the Gecko tree gets indexed in half a second.

Caching would be a good idea too, or at least incremental re-indexing.

[jamesona]

This would be HUGE for myself, and my team. Our company handles a lot of very wide repos, and the sum of the projects fuzzy-finder tries to index ends up being right around 1M inodes.

[arielnoname]

anything on this? keeps happening. even with small projects

[alxtz]

@arielnoname if you have file-icon installed, checkout this issue for the root cause #269

[mzhaase]

Is there any progress on this? Happens even without file-icon. Some cache option would be nice.

[rafeca]

Hey folks, this will get substantially improved by #369