becoming slow when searching long filenames #530

Closed
korovkin opened this Issue Feb 17, 2014 · 1 comment

Comments

Projects
None yet
2 participants
@korovkin

I have a repo of C/CPP/M/JS tree with about 100k files:
find . -type f | wc -l
107825

CtrlP works really well!

the only problem to report - the first 3-4 letters that i type in to search for a file, the UI responds almost immediately.
typing in more letters, freezes the UI for 2-3 seconds per a letter that i add.

I would love to profile this, in order to understand why this is happening.
any suggestions?

all this on a new retina MacBook Pro with a ssd drive, so i am assuming the hardware is not to blame for this.

@kien

This comment has been minimized.

Show comment Hide comment
@kien

kien Feb 17, 2014

Owner

The longer the search string is, the further down the file list the matcher has to dig for results. Over 100k entries is a lot for a List. As said in the other issue, you'll have to use an external matcher written in a more suitable language. There are at least a few of these matchers around, last time I looked.

Owner

kien commented Feb 17, 2014

The longer the search string is, the further down the file list the matcher has to dig for results. Over 100k entries is a lot for a List. As said in the other issue, you'll have to use an external matcher written in a more suitable language. There are at least a few of these matchers around, last time I looked.

@kien kien closed this Feb 17, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment