Re: Search performance - Scaling options Horizontally vs Vertically

2014-09-25 Thread Anne Veling
wrote: Can anyone answer this? -- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/Search-performance-Scaling-options-Horizontally-vs-Vertically-tp4063612p4063922.html Sent from the ElasticSearch Users mailing list archive at Nabble.com. -- You received

Re: Search performance - Scaling options Horizontally vs Vertically

2014-09-25 Thread pavan.bkv
if there are general guidelines for scaling and certification on TPS/number of concurrent users. Warm Regards, Pavan -- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/Search-performance-Scaling-options-Horizontally-vs-Vertically-tp4063612p4063985.html Sent from

Re: Search performance - Scaling options Horizontally vs Vertically

2014-09-25 Thread Mark Walkom
and certification on TPS/number of concurrent users. Warm Regards, Pavan -- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/Search-performance-Scaling-options-Horizontally-vs-Vertically-tp4063612p4063985.html Sent from the ElasticSearch Users mailing list archive

Re: Search performance - Scaling options Horizontally vs Vertically

2014-09-24 Thread pavan.bkv
Can anyone answer this? -- View this message in context: http://elasticsearch-users.115913.n3.nabble.com/Search-performance-Scaling-options-Horizontally-vs-Vertically-tp4063612p4063922.html Sent from the ElasticSearch Users mailing list archive at Nabble.com. -- You received this message

Re: Search performance - Scaling options Horizontally vs Vertically

2014-09-24 Thread Mark Walkom
://elasticsearch-users.115913.n3.nabble.com/Search-performance-Scaling-options-Horizontally-vs-Vertically-tp4063612p4063922.html Sent from the ElasticSearch Users mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups elasticsearch group

Search performance - Scaling options Horizontally vs Vertically

2014-09-16 Thread Venkat Pavan Bellapu Konda
I have observed that elastic search defaults the search thread pool to 3 X #of CPUs and even if you increase this to a fix # it does not really help as the threads start sharing the CPU cycles. Does this mean that to get same performance results for more concurrent searches I either have to