I think you confuse things and I disagree. If you see high CPU load, it is because your system runs tight of resources and tries harder to tackle these challenge automatically, e.g. by higher GC. It is not ES generating higher load just because of the index document count. There is no relation between a system tight on resources and the index document count of ES.
If you add nodes, the shards distribute over more nodes, this means scalability. When you scale out your system, you can process a higher number of queries concurrently. So with constant index document count, you have all kinds of CPU load, low and high. Jörg On Sun, Jul 27, 2014 at 1:40 PM, 'Fin Sekun' via elasticsearch < [email protected]> wrote: > > Thanks for your answers. > > @Jörg: > Of course sharding is primarly curcial for scalability, but it seems (and > nobody disagreed in this posts) that big indices lead to high CPU load, so > sharding is curcial for performance too. > > -- 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/CAKdsXoHecJ5cXAYN30rTKR4xqo6GzzonQXAnL703HNBWH7XFVQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
