Thanks for your reply. Yes, 100% CPU is used by SOLR (100% - I mean 1 core, not all cores), I'm totally sure.
I have more than 80 GB RAM on test machine and about 50 is cached as disk cache, SOLR uses about 8, Xmx=40G. I use GC1, but it can't be the problem, cause memory usage is much lower than GC start limit (45% of heap). I think, the problem can be in fully optimized index, and search over one big segment is much slower than parallel search over lot of segments, but it sounds weird, so I'm not sure. Setups with big indexes which I know are all with optimized indexes. Index scheme: <field name="text" type="text_general" indexed="true" stored="false" termVectors="true" termPositions="true" termOffsets="true" /> <field name="title" type="text_general" indexed="true" stored="false" termVectors="true" termPositions="true" termOffsets="true" /> <field name="cat" type="tint" indexed="true" stored="true" multiValued="false" required="true" omitNorms="true" omitTermFreqAndPositions="true"/> <field name="date" type="date" indexed="true" stored="false" omitNorms="true" omitTermFreqAndPositions="true"/> <field name="field1" type="int" indexed="true" stored="true" required="false" omitNorms="true" omitTermFreqAndPositions="true"/> <field name="field2" type="int" indexed="true" stored="true" required="false" omitNorms="true" omitTermFreqAndPositions="true"/> -- View this message in context: http://lucene.472066.n3.nabble.com/Simple-search-low-speed-tp4202135p4202157.html Sent from the Solr - User mailing list archive at Nabble.com.
