Hi,
We are using Solr 1.4 running 2 cores each containing ~90M documents. Each
core index size on the disk is ~ 120 G.
The machine is a 64-bit quad-core 64G RAM running Windows Server 2008.
Max heap size is set to 9G for the Tomcat process. Default caches are used.
Our queries are complex and in
facet
> request, the memory used to load up the facets for a particular field
> will not be evicted. So if you have lots and lots of facets, this
> could be a problem.
>
> On Wed, Apr 7, 2010 at 3:45 PM, Victoria Kagansky
> wrote:
> > Hi,
> > We are using Solr 1.4 run
:1527)
at java.lang.Thread.run(Thread.java:619)
On Thu, Apr 8, 2010 at 9:51 AM, Victoria Kagansky <
victoria.kagan...@gmail.com> wrote:
> The queries do require sorting (on int) and faceting. They should fetch
> first 200 docs.
> The current problematic core has 10 entries in
gt; (they include the relevance order, where filters don't care).
> Documents cache all of the fields in a document.
>
> On Thu, Apr 8, 2010 at 3:46 AM, Victoria Kagansky
> wrote:
> > I noticed now that the OutOfMemory exception occurs upon faceting
> queries.
> > Que
Hi,
We are using payloads for score boosting. For this purpose we've implemented
custom boosting QueryParser and similarity function. We followed
http://www.lucidimagination.com/blog/2009/08/05/getting-started-with-payloads/
.
On the other hand, we'd like to use dismax query handling because of it
