On my normal laptop I never bothered with performance as FARR was snappy enough. However on an older machine with a slower HD, I notice significant delays on startup. So I used the excellent Filemon from Sysinternals to log all file activity by FARR.
On startup, FARR seems to perform a complete scan through its specified folders. This requires ~3800 open/read/writes to be performed. This seems pointless as I have it set to show the history on startup.
Then when each letter is typed, FARR rescans everything again, another 3800 file operations per letter of the incremental search.
First off, can we stop FARR from reading the folders on startup, just read its history list. Second, some kind of directory cache would drop file access a lot and speed up the incremental search. I'm not suggesting a permanent cache, only a memory cache. It may consume some extra memory, but I believe you/Windows flush memory when FARR is hidden after a launch anywayso that would not be permanent.