Will do so. Thanks.
Are there any metrics on how to compute memory requirements (based on
doc average size, number of sorted fields, number of indexed documents +
number of new document / day) ?
Thanks
Christophe
Mark Miller wrote:
You need to setup a warming query that sorts so that the initial long
query is done behind the scenes. Users first query will then be fast.
Solrconfig.
- Mark
On Oct 18, 2008, at 1:34 AM, christophe <[EMAIL PROTECTED]>
wrote:
Here are the memory parameters I'm using now(Tomcat): -Xms2024m
-Xmx2024m
With those values, the second query is way faster. Only the first one
is very slow.
Thanks for the tip.
However, I'm wondering if will be enough and I will not hit the same
issues when I will have many users searching at the same time: I will
do a stress test to check this.
Thanks
Christophe
christophe wrote:
It is slow each time I run it. (I test it from the Solr admin
console or from a JAVA program using the Http client).
I do not get the OOM each time.
Thx
Christophe
Otis Gospodnetic wrote:
Is the sorted query slow only the first time or every time you run it?
You got an OOM? What -Xmx value are you using? Try increasing it.
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
----- Original Message ----
From: christophe <[EMAIL PROTECTED]>
To: solr-user@lucene.apache.org
Sent: Friday, October 17, 2008 1:28:52 PM
Subject: Sorting performance
Hi,
I'm doing some tests with Solr1.3
I have loaded around 7M documents, each with a few stored and
indexed fields.
This query: text:sometext returns the results, sorted by score in
a few milliseconds. (I display 10 out of 8747 matched documents)
This one: text:sometext;id desc takes something like 60s or more
to return the data (when it doesn't fails with an out of memory
error). (id is a string type).
I have tried to display only id, same results.
Any ideas ? I'm sure I'm doing something wrong.....
My schema is based on the sample, with the following fields:
/> multiValued="true" />
default="NOW" multiValued="false"/>
Thanks
Christophe
