Hey,
2015-02-24 16:49 GMT+01:00 Hardy Ferentschik :
> > * There are two types of tests in core: a) unit tests for stuff in core
> > itself and b) the "backendtck" which are high-level (i.e.
> Session/EM-level)
> > tests and which are executed for all backends.
>
> Wouldn't it make sense to have t
> * There are two types of tests in core: a) unit tests for stuff in core
> itself and b) the "backendtck" which are high-level (i.e. Session/EM-level)
> tests and which are executed for all backends.
Wouldn't it make sense to have these backendtck tests defined in a dedicated
module? When you me
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
