: nearly 100 percent and no queries were answered. I found out that
: "warming" the server with serial queries, not parallel ones, bypassed
: this problem (not to be confused with warming the caches!). So after a
Note that you can have Solr do this automatically for you in both
firstSearcher and
Hi,
Chris Hostetter wrote:
This is a fairly typical Lucene issue (ie: not specific to Solr)...
Ah, I see. I should really put more attention on Lucene. But when
working with Solr I sometimes forget about the underlying technology.
Sorting on a field requires building a FieldCache for every d
On 6/14/06, Chris Hostetter <[EMAIL PROTECTED]> wrote:
Off the top of my head, i don't remember if omiting norms for fields
reduces the amount of resident memory needed by the index
It does indeed. 1 byte per document for the indexed field.
-Yonik
This is a fairly typical Lucene issue (ie: not specific to Solr)...
Sorting on a field requires building a FieldCache for every document --
regardless of how many documents match your query. This cache is reused
for all searches thta sort on that field.
For things like Integers and Floats, the
Hello,
I have a new problem with OutOfMemory errors.
As I reported before, we have an index with more than 10 million
documents and 23 fields. Recently I added a new field which we will only
use for sorting purposes (by "adding" I mean building a new index). But
it turned out that every query
