My index has 76 million documents, I split it to 20 indexs because the
size of index is 33G. I deploy 20 shards for search response performence on
ec2's 20 instances.But when i wan't to update some doc, it means i must
traversal each index , and find the document is in which shard index, and
u
I split my docs to 100 indexs,I deploy the 100 indexs on 10 ec2 m2.4xLarge
instances for solr shards. it means each instance has 10 solr cores. it cost
4 to 10 seconds only for search when I test hundred concurrent threads,and
now I have 1000 online users per sencond, the user must wait for mor
In addition,my index has only two store fields, id and price, and other
fields are index. I increase the document and query cache. the ec2
m2.4xLarge instance is 8 cores, 68G memery. all indexs size is about 100G.
--
View this message in context:
http://lucene.472066.n3.nabble.com/my-index-has-5
thanks Toke,Once I've used "EBS" , I think that it can improve the I/O
performence, but it's not obvious better.so, maybe I/O is not the important
problem. thanks for your answer.
--
View this message in context:
http://lucene.472066.n3.nabble.com/my-index-has-500-million-docs-how-to-improve-sol
thanks,Lance Norskog-2. I've tested the EBS, but it's not better. so ,maybe I
have to optimize my solr config for ec2 m2.4xlarge.this kind computer config
is :
cpu units: 26 ECUs
cpu cores: 8
memery: 68G
solrconfig.xml content:
${solr.abortOnConfigurationError:true}
5G memory per JVM
--
View this message in context:
http://lucene.472066.n3.nabble.com/my-index-has-500-million-docs-how-to-improve-solr-search-performance-tp1902595p2819179.html
Sent from the Solr - User mailing list archive at Nabble.com.
