Hi Sanne,
I would not see a use for such an intense CPU hit since we intend to run it
as an autocomplete against forum posts titles (e.g. stackoverflow). So,
that would be changing on a continuous basis.
A cron job would suit just fine for that. We can tune that to our needs.
Cheers,
Marc
__
Hi Marc,
I didn't run any real performance test with it myself yet, but what
I'm understood from other Lucene users is that with the finite state
machine approach for auto-suggestion, the "index" (more appropriately
the state machine) isn't suited for real-time rebuilding.
We'll have to create a m
Lucene 4.x offers some interesting new functionality with regards to
autosuggest and google style suggestions.
As part of this functionality, as I understand it, the suggester builds a
separate index based on the available data with a specific .build()
function.
I'm assuming that this separate in
