Although many shards mean higher concurrency, a single shard also has very high concurrency. ES concurrency is implemented independent of the number of shards and is very flexible in configuration of thread pools and modules.
The default settings are for a small ES system which can scale to a around 5 nodes, so if you have a powerful machine, you will see that more than one shard gives better experience simply because the default settings are not designed for being limited to a single node. 50 shards per node is quite high and needs heavy adjustment at other places unless you go for a total number of around 50 nodes in the cluster, so I do not recommend high number of shards by default. Jörg On Mon, Apr 14, 2014 at 7:04 PM, <[email protected]> wrote: > Thanks guys, > yes I already have refresh interval at -1 > > What I'm suggesting is that to support multiple client threads say : 50 > then it seems that 50 shards is a big help. > ie more shards equals more concurrency. > > Thanks. > > -- > 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/1b531518-ee7c-424d-a238-eb92c3e59d6d%40googlegroups.com > . > 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/CAKdsXoHoRxLGze22d8PgrjsmWff6FndAqafZx%2BN5J3WSd%3DSYVw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
