lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lemke, Michael SZ/HZA-ZSW" <lemke...@schaeffler.com>
Subject RE: Facet performance
Date Tue, 22 Oct 2013 15:22:55 GMT
On Tue, October 22, 2013 9:23 AM Toke Eskildsen wrote:
>On Mon, 2013-10-21 at 16:57 +0200, Lemke, Michael SZ/HZA-ZSW wrote:
>> QTime fc:
>>        never returns, webserver restarts itself after 30 min with 100% CPU load
>
>It might be because it dies due to garbage collection. But since more
>memory (as your test server presumably has) just leads to the too many
>values-error, there isn't much to do.

Essentially, fc is out then.

>
>> QTime=41205              facet.prefix=            q=frequent_word          numFound=44532
>> 
>> Same query repeated:
>> QTime=225810             facet.prefix=            q=ottomotor              numFound=909
>> QTime=199839             facet.prefix=            q=ottomotor              numFound=909
>
>I am stumped on this, sorry. I do not understand why the 'ottomotor'
>query can take 5 times as long as the 'frequent_word'-one.

I looked into this some more this morning.  I noticed the java process was doing
a lot of I/O as shown in Process Explorer.  For the frequent_word it read about 
180MB, for ottomotor is was about seven times as much, ~ 1,200 MB.

jconsole didn’t show anything unusual according to our more experienced Java 
experts here.  Nor was the machine swapping.

Is it possible to screw up an index such that this sort of faceting leads to
constant reading of the index?  Something like full table scans in a db?

Michael
Mime
View raw message