Thanks for bringing closure on this, it'll probably help others too!
Erick
On Thu, Jul 5, 2012 at 12:28 PM, Anatoli Matuskova
wrote:
> Found why!
> On Solr 1.4 dismax param mm defaults to 1 if not specified, which is
> equivalent to AND. On Solr 4.0 if mm is not specified, the default operator
>
This is rather surprising. I know some defaults have changed between
1.4 and 4.0,
so the first thing I'd do is try some of your sample queries with
&debugQuery=on and
compare the debug info to see if you're executing more complex queries without
meaning to.
Also, dismax is deprecated in favor of e
Found why!
On Solr 1.4 dismax param mm defaults to 1 if not specified, which is
equivalent to AND. On Solr 4.0 if mm is not specified, the default operator
is used, which defaults to OR. That made return much more results for each
query I was running, increasing the response time and the CPU usage.
Hello,
I'm testing solr-4.0-alpha compared to 1.4. My index is optimized to one
segment. I've seen a decrease in memory usage but a very high increase in
CPU. This high cpu usage ends up giving me slower response times with 4.0
than 1.4
The server I'm using: Linux version 2.6.30-2-amd64 16 2.26GHz
