# ES Hardware Profiles **URL:** \ **Category:** Elasticsearch\ **Created:** [December 2, 2011, 4:53pm UTC](https://discuss.elastic.co/t/es-hardware-profiles/6055 "2011-12-02T16:53:21Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Michael\_Sick](https://avatars.discourse-cdn.com/v4/letter/m/22d042/32.png) [@Michael\_Sick](https://discuss.elastic.co/u/Michael_Sick)\ **Post date:** [December 2, 2011, 4:53pm UTC](https://discuss.elastic.co/t/es-hardware-profiles/6055/1 "2011-12-02T16:53:21Z")
I'm looking for a baseline server recommendation for running ES in a cluster. When I've reviewed other threads, there is little in the way of specifics (though my search may not have been exhaustive). I understand that there are many variables but I think a blessed baseline and some specific guidelines would be helpful to those getting started and those moving towards production. A set of recommendations like: [http://webcache.googleusercontent.com/search?q=cache:UjPiR\_xOhEwJ:hortonworks.com/best-practices-for-selecting-apache-hadoop-hardware/+&cd=4&hl=en&ct=clnk&gl=us](http://webcache.googleusercontent.com/search?q=cache:UjPiR_xOhEwJ:hortonworks.com/best-practices-for-selecting-apache-hadoop-hardware/+&cd=4&hl=en&ct=clnk&gl=us) (sorry the uncached version is password protected and I don't see a signup) or > **[Cloudera's Support Team Shares Some Basic Hardware Recommendations - Cloudera...](http://blog.cloudera.com/blog/2010/03/clouderas-support-team-shares-some-basic-hardware-recommendations/)** > > Refer to this post (Aug. 28, 2013) for state-of-the-art recommendations about hardware selection for new Hadoop clusters. > Read more would be very helpful. Aside from the baseline, I'd like to better understand: 1. How does using ES as the primary data store impact the baseline? 2. Baseline networking recommendations 3. What's the max percent of data that should be on any one node for responsive fail over? 4. Is there any role for a SSD drive on a node for fast swap? I remember Shay speaking of swapping Filter/Cache data to disk and it would seem reasonable for that use case. Didn't know if there were any current uses. If we can get some consensus here on baseline and rules, I'd be more than willing to write this up for posting on the ES site (or modifying / updating an existing resource if needed). ---
**Author:** ![Gustavo\_Maia](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gustavo_maia/32/2183_2.png) [@Gustavo\_Maia](https://discuss.elastic.co/u/Gustavo_Maia)\ **Post date:** [December 2, 2011, 8:41pm UTC](https://discuss.elastic.co/t/es-hardware-profiles/6055/2 "2011-12-02T20:41:57Z")
Hi Michael, I have 2 servers on the Amazon, with the following configuration: High-CPU Extra Large Instance 7 GB of memory 20 EC2 Compute Units (8 virtual cores with 2.5 EC2 Compute Units each) 1690 GB of instance storage 64-bit platform I/O Performance: High API name: c1.xlarge Each instance has 4 hds. But I'm finding the search a little slow when I'm indexing and searching the same time. I do not know if you have anything to do with the plugin to make copies in S3. My ES is configured with two shards and one replica. The seek time is 500ms up to a volume index of 1GB. 2011/12/2 Michael Sick [michael.sick@serenesoftware.com](mailto:michael.sick@serenesoftware.com): > I'm looking for a baseline server recommendation for running ES in a > cluster. When I've reviewed other threads, there is little in the way of > specifics (though my search may not have been exhaustive). I understand that > there are many variables but I think a blessed baseline and some specific > guidelines would be helpful to those getting started and those moving > towards production. > > A set of recommendations like: > [http://webcache.googleusercontent.com/search?q=cache:UjPiR\_xOhEwJ:hortonworks.com/best-practices-for-selecting-apache-hadoop-hardware/+&cd=4&hl=en&ct=clnk&gl=us](http://webcache.googleusercontent.com/search?q=cache:UjPiR_xOhEwJ:hortonworks.com/best-practices-for-selecting-apache-hadoop-hardware/+&cd=4&hl=en&ct=clnk&gl=us) (sorry > the uncached version is password protected and I don't see a signup) > > or > [http://www.cloudera.com/blog/2010/03/clouderas-support-team-shares-some-basic-hardware-recommendations/](http://www.cloudera.com/blog/2010/03/clouderas-support-team-shares-some-basic-hardware-recommendations/) > > would be very helpful. Aside from the baseline, I'd like to better > understand: > > How does using ES as the primary data store impact the baseline? > Baseline networking recommendations > What's the max percent of data that should be on any one node for responsive > fail over? > Is there any role for a SSD drive on a node for fast swap? I remember Shay > speaking of swapping Filter/Cache data to disk and it would seem reasonable > for that use case. Didn't know if there were any current uses. > > If we can get some consensus here on baseline and rules, I'd be more than > willing to write this up for posting on the ES site (or modifying / updating > an existing resource if needed). -- Gustavo Maia ---
**Author:** ![Michael\_Sick](https://avatars.discourse-cdn.com/v4/letter/m/22d042/32.png) [@Michael\_Sick](https://discuss.elastic.co/u/Michael_Sick)\ **Post date:** [December 8, 2011, 11:52pm UTC](https://discuss.elastic.co/t/es-hardware-profiles/6055/3 "2011-12-08T23:52:50Z")
Hi Gustavo, Thanks for the note - sorry for the lag. I did a demo with 8 servers of the same configuration that you're using but was never able to tax them very much (we were hitting limits on the HBase portion of the work well before we were limited by ES). One thing I can say was that the performance was pretty variable for writing to ES, often it screamed but it could lag on the same test an hour later. --Mike On Fri, Dec 2, 2011 at 3:41 PM, Gustavo Maia [gustavobbmaia@gmail.com](mailto:gustavobbmaia@gmail.com)wrote: > Hi Michael, > > I have 2 servers on the Amazon, with the following configuration: > > High-CPU Extra Large Instance > > 7 GB of memory > 20 EC2 Compute Units (8 virtual cores with 2.5 EC2 Compute Units each) > 1690 GB of instance storage > 64-bit platform > I/O Performance: High > API name: c1.xlarge > > Each instance has 4 hds. > But I'm finding the search a little slow when I'm indexing and > searching the same time. > I do not know if you have anything to do with the plugin to make copies in > S3. > My ES is configured with two shards and one replica. > The seek time is 500ms up to a volume index of 1GB. > > 2011/12/2 Michael Sick [michael.sick@serenesoftware.com](mailto:michael.sick@serenesoftware.com): > > > I'm looking for a baseline server recommendation for running ES in a > > cluster. When I've reviewed other threads, there is little in the way of > > specifics (though my search may not have been exhaustive). I understand > > that > > there are many variables but I think a blessed baseline and some specific > > guidelines would be helpful to those getting started and those moving > > towards production. > > > > A set of recommendations like: > > [http://webcache.googleusercontent.com/search?q=cache:UjPiR\_xOhEwJ:hortonworks.com/best-practices-for-selecting-apache-hadoop-hardware/+&cd=4&hl=en&ct=clnk&gl=us](http://webcache.googleusercontent.com/search?q=cache:UjPiR_xOhEwJ:hortonworks.com/best-practices-for-selecting-apache-hadoop-hardware/+&cd=4&hl=en&ct=clnk&gl=us) > (sorry > > > the uncached version is password protected and I don't see a signup) > > > > or > > [http://www.cloudera.com/blog/2010/03/clouderas-support-team-shares-some-basic-hardware-recommendations/](http://www.cloudera.com/blog/2010/03/clouderas-support-team-shares-some-basic-hardware-recommendations/) > > > would be very helpful. Aside from the baseline, I'd like to better > > understand: > > > > How does using ES as the primary data store impact the baseline? > > Baseline networking recommendations > > What's the max percent of data that should be on any one node for > > responsive > > fail over? > > Is there any role for a SSD drive on a node for fast swap? I remember > > Shay > > speaking of swapping Filter/Cache data to disk and it would seem > > reasonable > > for that use case. Didn't know if there were any current uses. > > > > If we can get some consensus here on baseline and rules, I'd be more than > > willing to write this up for posting on the ES site (or modifying / > > updating > > an existing resource if needed). > > -- > Gustavo Maia ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 3:46am UTC](https://discuss.elastic.co/t/es-hardware-profiles/6055/4 "2017-07-06T03:46:01Z")