Thanks! So per your experience, is Elasticsearch query more CPU-bound or IO-bound? Anyway, I will do more perf testing with real data on different VMs to find out the best CPU & Memory combination for my case.
On Wednesday, April 29, 2015 at 9:57:12 PM UTC+8, Jörg Prante wrote: > First you need to find out if your workload is CPU-bound or if it is > network-bound. > > If CPU-bound, go for the virtual machine with best CPU equipment. > > If network bound, go for the virtual machine that offers best network > connectivity. > > It is very hard to get precise numbers for performance metrics in public > virtual machines because there are many others using the same resources at > the the same time in an unpredictable way. > > Jörg > > > On Wed, Apr 29, 2015 at 11:02 AM, Xudong You <xudon...@gmail.com > <javascript:>> wrote: > >> I want better maximum throughput for all queries. >> As for VM vs Physical machines. I agree that physical machines beat VM, >> but our strategy is to move our platform to cloud, so VM is only choice. >> >> On Wednesday, April 29, 2015 at 4:30:19 PM UTC+8, Jörg Prante wrote: >>> >>> Can you specify what kind of performance you mean? >>> >>> - mimimal response time for a single query >>> - maximum throughput for all queries >>> >>> For maximum performance, all kind of virtual machines are a bad choice >>> in comparison to physical machines in your own data center. >>> >>> Jörg >>> >>> >>> On Wed, Apr 29, 2015 at 4:17 AM, Xudong You <xudon...@gmail.com> wrote: >>> >>>> hi, >>>> I am building ES on cloud Virtual machines, the cloud platform provides >>>> different tier VMs to choose, say, 4 CPU cores, 28G memory, or 8 CPU >>>> cores, >>>> 14G memory etc. Different kind VM has different cost. To save our cost, I >>>> want to choose the VM whose cost not exceed our budget and has best >>>> performance or query. >>>> So, from query performance point of view, should I choose VM with more >>>> CPU cores or more memory? Anyone has experience on the best combination of >>>> CPU & Memory for ES 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 elasticsearc...@googlegroups.com. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/elasticsearch/e449f0bb-5c92-4aee-84f5-285171e8070c%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/elasticsearch/e449f0bb-5c92-4aee-84f5-285171e8070c%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 elasticsearc...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/5e1aee9b-f2d5-4340-9a8e-d30b786cda5a%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/5e1aee9b-f2d5-4340-9a8e-d30b786cda5a%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 elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/4ebe219f-9422-48ed-a84f-d8606f16a7bf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
