1. Use filter queries
> Here a example of query, there are any incorrect o anything that can I
> change?
> http://xxx:8893/solr/candidate/select/?q=+(IdCandidateStatus:2)+(IdCobranded:3)+(IdLocation1:12))+(LastLoginDate:[2011-08-26T00:00:00Z
> TO 2012-08-28T00:00:00Z])
What is the logic here? Are
http://lucidworks.lucidimagination.com/display/solr/Distributed+Search+with+Index+Sharding
Regards
Pravesh
--
View this message in context:
http://lucene.472066.n3.nabble.com/Query-Time-problem-on-Big-Index-Solr-3-5-tp4003660p4004630.html
Sent from the Solr - User mailing list archive at Nabble.com.
" required="true" />
> required="true" />
> required="true" />
> stored="true" required="true" />
> stored="true"
> required="true" />
> required="true" />
> required="true" />
> stored="true" required="true" />
> stored="true" required="true" />
> stored="true"
> required="true" />
> required="true" />
> required="true" />
> required="true" />
> required="true" />
> required="true" />
> required="true" />
> required="true" />
> required="true" />
> required="true" />
> required="true" />
> required="true" />
> stored="true"
> required="false" multiValued="true" />
> required="true" />
> required="true" />
> required="true" />
> required="true" multiValued="false"/>
> required="true" multiValued="false"/>
> stored="true" required="true"/>
> required="false" multiValued="true" />
> stored="true"
> required="true" />
> stored="true" required="false" multiValued="true" />
> stored="false"/>
>
> *Solconfig.xml:*
> LUCENE_35
> ...
> class="${solr.directoryFactory:solr.StandardDirectoryFactory}"/>
> false
> 32
> 10
> false
> true
> ...
> 131072
> autowarmCount="8048"/> initialSize="8048" autowarmCount="8048"/> class="solr.LRUCache" size="262144" initialSize="8048"
>
> autowarmCount="8048"/>true60
> 200
> ...
> false
> 2
>
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Query-Time-problem-on-Big-Index-Solr-3-5-tp4003660.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
apply to other
fields which require very less analysis or have limited unique fields.
Thanx
Pravesh
--
View this message in context:
http://lucene.472066.n3.nabble.com/Query-Time-problem-on-Big-Index-Solr-3-5-tp4003660p4004437.html
Sent from the Solr - User mailing list archive at Nabble.com.
t not as ranges). This might
give an indication of the kind of gain you could get with trie field types
for your numeric fields.
-- Jack Krupansky
-Original Message-
From: mpcmarcos
Sent: Tuesday, August 28, 2012 5:02 AM
To: solr-user@lucene.apache.org
Subject: Query Time problem o
g.xml:*
LUCENE_35
...
false
32
10
false
true
...
131072
true60
200
...
false
2
--
View this message in context:
http://lucene.472066.n3.nabble.com/Query
... 21 more
Charles-André Martin
800 Square Victoria
Montréal (Québec) H4Z 0A3
Tél : (514) 504-2703
-Message d'origine-
De : simon [mailto:mtnes...@gmail.com]
Envoyé : August-10-11 1:52 PM
À : solr-user@lucene.apache.org
Objet : Re: query time problem
Off the top of my hea
Off the top of my head ...
Can you tell if GC is happening more frequently than usual/expected ?
Is the index optimized - if not, how many segments ?
It's possible that one of the shards is behind a flaky network connection.
Is the 10s performance just for the Solr query or wallclock time at
t
Hi,
I've noticed poor performance for my solr queries in the past few days.
Queries of that type :
http://server:5000/solr/select?q=story_search_field_en:(water boston) OR
story_search_field_fr:(water boston)&rows=350&start=0&sort=r_modify_date
desc&shards=shard1:5001/solr,shard2:5002
