Gunther, Andrew wrote:
Yes most all terms are multi-valued which I can't avoid. Since the data is coming from a library catalogue I am translating a subject field to make a subject facet. That facet alone is the biggest, hovering near 39k. If I remove this facet.field things return faster. So am I to assume that this particular field bogging down operations and there are no other optimization options besides cutting down this field?
Andrew, I haven't yet found a successful way to implement the SOLR faceting for library catalog data. I developed my own system, so for every query, I first query 20 records. Let's say it find 1000 records and returns the 20 records. Then I make a second query returning all 1000 records and build my own facets based on the 1000 records. It's a bit faster than using SOLRs faceting system, but as you said. For large records it still takes a bit of time. I implemented it using AJAX so it doesn't slow down the loading of the page.
I'd be curious if anyone has been able to find a better way using SOLRs faceting system
Andrew
