[KinoSearch] optimize broken?
mark at thinkfoo.com
Thu Aug 14 10:48:32 PDT 2008
I'm doing some parallel indexing by firing off batches using gearman,
then once a task completes using ->add_invindex() to merge the batch to
a single index. After all batches are merged I optimize the index. This
works pretty reliably with around 27m records.
However, in the latest trunk of KinoSearch, ->finish(optimize => 1) no
longer seems to work. It returns almost immediately and none of the
segments are collapsed. The index is searchable but it's pretty slow.
The test suite runs successfully. Any ideas?
p.s. I was pleased to see indexing speed significantly improved in the
latest trunk. It's now taking perhaps half the time of the
KinoSearch-0.20_051 cpan release and getting close to speeds I'm used to
seeing with Solr.
KinoSearch mailing list
KinoSearch at rectangular.com
More information about the kinosearch