Infrastructure for Elastissearch


(Srinivasa Rao Myneni) #1

I'm new to Elastic-search and we have a requirement to implement it for 300 GB SQL Server data which contains documents also. I'm looking what will be the optimal infrastructure (like RAM, Disk Space, no of cores, no of nodes, no of shards, replicas etc.) to setup Elastic-search based on below parameters,

• Size of data to be Indexed: 300 GB
• No of concurrent users: 100
• No of concurrent queries: 100
• No of queries in 5 sec Span: 300
• Expected response time for results: less than 1 sec
• No of Users to access the System: 2000

Forgot to mention that we are looking this infrastructure on windows (mostly on Azure Platform as VM's).


(David Pilato) #2

May I suggest you look at the following resources:


(Christian Dahlqvist) #3

Getting it right will probably require some benchmarking, in which case the following resources may also be useful:

https://www.elastic.co/elasticon/conf/2016/sf/quantitative-cluster-sizing

https://www.elastic.co/webinars/using-rally-to-get-your-elasticsearch-cluster-size-right


(Srinivasa Rao Myneni) #4

forgot to mention that we are looking this infrastructure on windows (mostly on Azure Platform as VM's).


(Srinivasa Rao Myneni) #5

looks like Rally does not support Windows and is only actively tested on MacOS and Linux. Before installing Rally, please ensure that the following packages are installed.


(system) #6

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.