What we do in our application is exactly what Robert described. We index
Products, not variants. The variant data (colour, size etc.) is denormalised
into the product document at index time. We then facet on the variant
attributes and get product count instead of variant count.
What you're see
We found that optimising too often killed our slave performance. An optimise
will cause you to merge and ship the whole index rather than just the relevant
portions when you replicate.
The change on our slaves in terms of IO and CPU as well as RAM was marked.
Andrew
Sent on the run.
On 23/
With Solr 4.0 you could use relevance functions to give a query time boost if
you don't have the information at index time.
Alternatively you could do term facet based autocomplete which would mean you
could sort by count rather than any other input.
Andrew
Sent on the run.
On 20/01/2012,
