I already replied to you on stack overflow but your response there and the schema.xml definition here are contrary to each other.
You are using a textSpell field which is tokenized as a unique key. As I mentioned on stack overflow, it is a bad idea. Yes, it will impact performance as well as lead to duplicate documents. Switch to a "string" or int/long field and you should be fine regardless of what it is named. On Tue, Jan 20, 2015 at 8:28 AM, Nitin Solanki <nitinml...@gmail.com> wrote: > Hi, > I am working on solr 4.10.2. I have been trapped into > the *performance > issue* where I have indexed 600MB data on 4 shards with single replicas > each. I have defined 2 fields (ngram and frequency). I have removed ID > field and replaced it with ngram field. Therefore, Search performance is > getting low and taking *QTime = 134 ms* which is not well for my task. > > *Schema.xml(sample part) *:- > *ngram field* - <field name="ngram" type="textSpell" indexed="true" > stored="true" required="true" multiValued="false"/> > > <fieldType name="textSpell" class="solr.TextField" > positionIncrementGap="100"> > <analyzer type="index"> > <tokenizer class="solr.StandardTokenizerFactory"/> > <filter class="solr.ShingleFilterFactory" maxShingleSize="3" > minShingleSize="2" outputUnigrams="true"/> > </analyzer> > <analyzer type="query"> > <tokenizer class="solr.StandardTokenizerFactory"/> > <filter class="solr.ShingleFilterFactory" maxShingleSize="3" > minShingleSize="2" outputUnigrams="true"/> > </analyzer> > </fieldType> > > I have posted same problem on Stackoverflow > < > http://stackoverflow.com/questions/27983291/replacing-id-with-another-will-degrade-performance-in-solr/27984428?noredirect=1#comment44431492_27984428 > > > but no able to get correct solution. Please help me. > > Thanks and Regards, > Nitin Solanki. > -- Regards, Shalin Shekhar Mangar.
