Glad to hear you have a solution
Best,
Erick
On Thu, Nov 7, 2013 at 5:12 PM, Patanachai Tangchaisin <
patanachai.tangchai...@wizecommerce.com> wrote:
> Hi Erick,
>
> About the size of filter cache, previously we set it to 4,000.
> After we faced this problem, we changed it to 10,000.
> Stil
Hi Erick,
About the size of filter cache, previously we set it to 4,000.
After we faced this problem, we changed it to 10,000.
Still at size of 10,000 (always full), hitratio was 0.78 and "eviction" was as high as
"insertion".
About 100% Cpu, yes, it was Solr using it.
I profiled an app, it was
Yeah, Solr's fq cache is pretty simple-minded,
order matters. There's no good way to improve
that except try to write your fq queries in the
same order. It's actually quite tricky to
disassemble/reassemble arbitrary queries to fix
this problem.
But in your case, you could write a custom query
comp
Hello,
We are running our search system using Apache Solr 4.2.1 and using
Master/Slave model.
Our index has ~100M document. The index size is ~20gb.
The machine has 24 CPU and 48gb rams.
Our response time is pretty bad, median is ~4 seconds with 25
queries/second.
We noticed a couple of things
