Skip characters in search-compile or precompile static text?
Posted: Tue Jan 31, 2017 9:59 am
All,
Search for small substrings in larger strings is enabled, and customers and in-house reviewers love it.
But now, compiling the "search entry cache" is very slow.
Building and publishing takes hours, when it formerly took 20 minutes for a given project.
Substring search needs to stay, so I can't just switch off.
I eliminated some paragraph-long and sentence-long strings-with-no-spaces, and that yielded a speed increase, but a build is still longer than two hours.
Is there a place I can tell Flare to treat an underscore and a colon as a word separator like it does a space?
Also very helpful would be the ability to pre-compile search for specific topics that tend to remain static, release-over-release. This would leave a smaller set of topics to scan fresh each time the search database is built. Is that an option?
Search for small substrings in larger strings is enabled, and customers and in-house reviewers love it.
But now, compiling the "search entry cache" is very slow.
Building and publishing takes hours, when it formerly took 20 minutes for a given project.
Substring search needs to stay, so I can't just switch off.
I eliminated some paragraph-long and sentence-long strings-with-no-spaces, and that yielded a speed increase, but a build is still longer than two hours.
Is there a place I can tell Flare to treat an underscore and a colon as a word separator like it does a space?
Also very helpful would be the ability to pre-compile search for specific topics that tend to remain static, release-over-release. This would leave a smaller set of topics to scan fresh each time the search database is built. Is that an option?