Hi AK, It's a little hard to make a recommendation like this because it really depends on how you've structured your logical and physical index, how much historical data you want to keep and query, what sort of queries you run, how fast you need things to be, etc.
Something like SPM for Elasticsearch (http://sematext.com/spm/ ) can tell you about where your bottleneck is - maybe it's CPU, maybe it's RAM, maybe it's IO, or something else. Based on that info you will see which instances you should get, how many you'll need, etc. Otis -- Elasticsearch Performance Monitoring * Log Analytics * Search Analytics Solr & Elasticsearch Support * http://sematext.com/ On Wednesday, August 13, 2014 5:38:10 PM UTC+2, AK wrote: > > Hi, > > I recently launched ELK and I'm receiving about 3,000,000 - 8,000,000 docs > per day (~ 5GB) > I'm running on AWS on a small server, and after a week of data collection > the system becomes very very slow, mainly when I am looking for data older > than 2 days. > Do you have a recommendation for servers in points such as cpu, memory and > iops and elstic settings like shards. > > Thanks > AK > > > > > -- 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/c984032b-3a9c-453d-94d5-1ecda9b718c9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
