its return 0 but multiple
> document have the same word.
>
> i have try with different field type : text_gen, text_en_splitting, String
> but i didnt get exact result
> can you please help for this.
>
>
>
>
>
> --
> View this message in context:
> http://l
dnt get exact result
can you please help for this.
--
View this message in context:
http://lucene.472066.n3.nabble.com/SOLR-4-not-utilizing-multi-CPU-cores-tp4105058p4133256.html
Sent from the Solr - User mailing list archive at Nabble.com.
After debugging it seems that Query Parser code in Surround Parser is
giving an issue in queries with Common Words. Has anyone tried Surround and
Common Grams with SOLR 4?
On Thu, Dec 5, 2013 at 7:00 PM, Daniel Collins wrote:
> Fair enough, I'm not famiilar with Surround parser, but it does look
Fair enough, I'm not famiilar with Surround parser, but it does look like
some logic has changed there.
On 5 December 2013 12:38, Salman Akram
wrote:
> Here is the response to your 2 questions:
>
> 1- Started from fresh Solr 4 config and modified custom stuff.
>
> 2- Index is same and optimized.
Here is the response to your 2 questions:
1- Started from fresh Solr 4 config and modified custom stuff.
2- Index is same and optimized.
However, as I said in a previous mail the issue seems to be Surround Query
Parser which is parsing the query in a different format.
On Thu, Dec 5, 2013 at 2:
I am not using Shards.
I gave more info in a previous mail but I know its a single index and what
you are saying makes sense but from what I could see in 1.4.1 that it was
better 'utilizing' the hardware resources available. I mean if the CPU is
free then why not do multi threading (if possible of
So I think I found one issue that somewhat explains the time difference but
not sure why this is happening. We are using Surround Query Parser. Below
is a two words query, both of them are in Common Grams list.
Query = "only be"
Here is what debug shows. I have highlighted the red part which is
d
Not sure if you are really stating the problem here.
If you don't use Solr sharding, (I also assume you aren't using SolrCloud),
and I'm guessing you are a single core (but can you confirm).
As I understand Solr's logic, for a single query on a single core, that
will only use 1 thread (ignoring u
More info on Cpu consumption: We have a server with 32 physical cores.
Same search when executed on SOLR 4.6 takes quite long and throughout only
uses 3% cpu (1 core).
Same search when executed on SOLR 1.4.1 takes much less time and on average
uses around 40-50% cpu.
On Thu, Dec 5, 2013 at 2:05
I missed one imp piece of info. Due to large size we have indexed the date
with Common Grams. All of the words in slow search are in common grams and
when I debug it, they query is made properly with common grams.
In debug all of the time is shown in process query time.
Let me know what other inf
Hi, I did moreless the same but didn't get that behaviour...could you give
us more details
Best,
Gazza
On 5 Dec 2013 06:54, "Salman Akram"
wrote:
> Hi,
>
> We recently upgraded to SOLR 4.6 from SOLR 1.4.1. Overall the performance
> went down for large phrase queries. On some analysis we have see
Hi,
We recently upgraded to SOLR 4.6 from SOLR 1.4.1. Overall the performance
went down for large phrase queries. On some analysis we have seen that
1.4.1 utilized multiple cpu cores for such queries but SOLR 4.6 is only
utilizing single cpu core. Any idea on what could be the reason?
Note: We ar
12 matches
Mail list logo
