I imagine that depends on lots of stuff. Are you doing elasticsearch:9200/_search or elasticsearch:9200/index/_search ? The former can take quite a while if you have lots index and lots of shards. If you can get away with not doing it, I would. The latter will only take a long time if you have tons of shards. It should otherwise be pretty quick.
On Tue, Jun 10, 2014 at 2:10 PM, <[email protected]> wrote: > We currently run our Elasticsearch (*v1.0.2*) cluster on *3 Nodes* with *5 > Shards and 1 Replication* Scheme. The total index size is about 70GB > (~140GB with replication). > > The Empty Search (/_search) query takes 500-600 ms to respond. Will adding > in more Nodes help in this case? The Servers are have 252gb of RAM and > 110gb for Heap. > > The Index uses the following analyzers - standard, lowercase, stop, > porter_stem. Will this degrade Query performance? > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/9941cfd1-d211-4706-aa45-6c545c66baff%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/9941cfd1-d211-4706-aa45-6c545c66baff%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAPmjWd3FBD_fDvejUwaf_L%3D8s4KzzLZmT%3DBJMyj9-5FeUs6YOA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
