For better results - you should align the number of nodes n with the shard count c, so that c/n = i where i is an integer - 7 million docs may be too few to see any effect, this depends on the node capacity - for higher perfomance, you should use one JVM per machine, not 4 virtual machines on one machine
The query response time will not get faster by adding nodes. The query response time on a single shard is limited by hardware factors (like CPU power, RAM, disk speed) and some software settings (ES settings, ES caches). The query response time will scale over nodes, that is, if you have saturated one node, you can add more nodes, start over to add more docs, while the query response time will not get higher by the number of added docs. The reason is, ES submits the queries to the shards on the nodes in parallel, so it makes no difference if there is one or thousands nodes in the cluster. Of course you should run query tests in parallel, if you want to measure the cluster capacity / throughput. Jörg On Mon, Mar 24, 2014 at 9:54 AM, Herbert Bodner <[email protected]>wrote: > > Are these results expected, that *the query response time does NOT > improve when adding an additional node?* > > -- 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/CAKdsXoGaMyKWYGkPnn8wo_kzm4W%2BoSv62bNQNU0G2Dws9pK1hg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
