# ES seems slow and ineffecient

**URL:** <https://discuss.elastic.co/t/es-seems-slow-and-ineffecient/18391>\
**Category:** Elasticsearch\
**Created:** [June 30, 2014, 8:40am UTC](https://discuss.elastic.co/t/es-seems-slow-and-ineffecient/18391 "2014-06-30T08:40:34Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dan\_Storm](https://avatars.discourse-cdn.com/v4/letter/d/2bfe46/32.png) [@Dan\_Storm](https://discuss.elastic.co/u/Dan_Storm)\
**Post date:** [June 30, 2014, 8:40am UTC](https://discuss.elastic.co/t/es-seems-slow-and-ineffecient/18391/1 "2014-06-30T08:40:34Z")

</div>

I have a cluster setup with three nodes.  
The three nodes are setup within LXC with 8GB of ram dedicated to each  
container. Heap size is set to 4GB on each and bootstrap.mlockall is set to  
true.

iptables has been setup to forward incoming traffic on port 9200 to the  
master node.

Heres an image of the diagnostics provided by HQ.

[http://i.imgur.com/z59W4hV.png](http://i.imgur.com/z59W4hV.png)  
I experience quite a few timeouts.  
The dedicated server is a 48GB RAM setup with 8 cores and SSD disks, so I  
would believe I have enough power to handle the load.

Can anyone see if there is something I should be aware of or something that  
I can do to make my

Thank you.

--  
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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/537e0142-a726-44f8-a1fb-e11faa51c052%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/537e0142-a726-44f8-a1fb-e11faa51c052%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 30, 2014, 10:25am UTC](https://discuss.elastic.co/t/es-seems-slow-and-ineffecient/18391/2 "2014-06-30T10:25:51Z")

</div>

Can you elaborate on the timeouts?

What Elasticsearch version, what java version?

Regards,  
Mark Walkom

Infrastructure Engineer  
Campaign Monitor  
email: [markw@campaignmonitor.com](mailto:markw@campaignmonitor.com)  
web: [www.campaignmonitor.com](http://www.campaignmonitor.com)

On 30 June 2014 18:40, Dan Storm [l33tnasty@gmail.com](mailto:l33tnasty@gmail.com) wrote:

> I have a cluster setup with three nodes.  
> The three nodes are setup within LXC with 8GB of ram dedicated to each  
> container. Heap size is set to 4GB on each and bootstrap.mlockall is set to  
> true.
> 
> iptables has been setup to forward incoming traffic on port 9200 to the  
> master node.
> 
> Heres an image of the diagnostics provided by HQ.
> 
> [http://i.imgur.com/z59W4hV.png](http://i.imgur.com/z59W4hV.png)  
> I experience quite a few timeouts.  
> The dedicated server is a 48GB RAM setup with 8 cores and SSD disks, so I  
> would believe I have enough power to handle the load.
> 
> Can anyone see if there is something I should be aware of or something  
> that I can do to make my
> 
> Thank you.
> 
> --  
> 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/537e0142-a726-44f8-a1fb-e11faa51c052%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/537e0142-a726-44f8-a1fb-e11faa51c052%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/537e0142-a726-44f8-a1fb-e11faa51c052%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/537e0142-a726-44f8-a1fb-e11faa51c052%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEM624bYb-EQJyeqJeSZmH-\_Jqc5szfSo1mgXuM6wR6hhCJuUg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEM624bYb-EQJyeqJeSZmH-_Jqc5szfSo1mgXuM6wR6hhCJuUg%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Dan\_Storm](https://avatars.discourse-cdn.com/v4/letter/d/2bfe46/32.png) [@Dan\_Storm](https://discuss.elastic.co/u/Dan_Storm)\
**Post date:** [June 30, 2014, 11:10am UTC](https://discuss.elastic.co/t/es-seems-slow-and-ineffecient/18391/3 "2014-06-30T11:10:37Z")

</div>

Hi Mark,

Java:  
java version "1.7.0\_55"  
OpenJDK Runtime Environment (IcedTea 2.4.7) (7u55-2.4.7-1ubuntu1~0.13.10.1)

ES is version 1.2.1

The timeouts happen when higher number of queries occur and ES has memory  
issues. But I'm unsure as to why the setup lacks memory.

On Monday, June 30, 2014 12:26:23 PM UTC+2, Mark Walkom wrote:

> Can you elaborate on the timeouts?
> 
> What Elasticsearch version, what java version?
> 
> Regards,  
> Mark Walkom
> 
> Infrastructure Engineer  
> Campaign Monitor  
> email: [ma...@campaignmonitor.com](mailto:ma...@campaignmonitor.com) \<javascript:\>  
> web: [www.campaignmonitor.com](http://www.campaignmonitor.com)
> 
> On 30 June 2014 18:40, Dan Storm \<[l33t...@gmail.com](mailto:l33t...@gmail.com) \<javascript:\>\> wrote:
> 
> > I have a cluster setup with three nodes.  
> > The three nodes are setup within LXC with 8GB of ram dedicated to each  
> > container. Heap size is set to 4GB on each and bootstrap.mlockall is set to  
> > true.
> > 
> > iptables has been setup to forward incoming traffic on port 9200 to the  
> > master node.
> > 
> > Heres an image of the diagnostics provided by HQ.
> > 
> > [http://i.imgur.com/z59W4hV.png](http://i.imgur.com/z59W4hV.png)  
> > I experience quite a few timeouts.  
> > The dedicated server is a 48GB RAM setup with 8 cores and SSD disks, so I  
> > would believe I have enough power to handle the load.
> > 
> > Can anyone see if there is something I should be aware of or something  
> > that I can do to make my
> > 
> > Thank you.
> > 
> > --  
> > 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](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/537e0142-a726-44f8-a1fb-e11faa51c052%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/537e0142-a726-44f8-a1fb-e11faa51c052%40googlegroups.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/537e0142-a726-44f8-a1fb-e11faa51c052%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/537e0142-a726-44f8-a1fb-e11faa51c052%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > .  
> > For more options, visit [https://groups.google.com/d/optout](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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5faadcf2-7845-4aab-a651-86bb09d5572e%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5faadcf2-7845-4aab-a651-86bb09d5572e%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [June 30, 2014, 2:47pm UTC](https://discuss.elastic.co/t/es-seems-slow-and-ineffecient/18391/4 "2014-06-30T14:47:21Z")

</div>

If you have one server with 48G RAM / 8 cores / SSD you should se up one  
Elasticsearch node because JVM is capable of managing it.

By setting up 3 nodes on just a single server, you only add overhead and  
the risk of timeouts and instability is higher.

Jörg

On Mon, Jun 30, 2014 at 10:40 AM, Dan Storm [l33tnasty@gmail.com](mailto:l33tnasty@gmail.com) wrote:

> I have a cluster setup with three nodes.  
> The three nodes are setup within LXC with 8GB of ram dedicated to each  
> container. Heap size is set to 4GB on each and bootstrap.mlockall is set to  
> true.
> 
> iptables has been setup to forward incoming traffic on port 9200 to the  
> master node.
> 
> Heres an image of the diagnostics provided by HQ.
> 
> [http://i.imgur.com/z59W4hV.png](http://i.imgur.com/z59W4hV.png)  
> I experience quite a few timeouts.  
> The dedicated server is a 48GB RAM setup with 8 cores and SSD disks, so I  
> would believe I have enough power to handle the load.
> 
> Can anyone see if there is something I should be aware of or something  
> that I can do to make my
> 
> Thank you.
> 
> --  
> 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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> To view this discussion on the web visit  
> [https://groups.google.com/d/msgid/elasticsearch/537e0142-a726-44f8-a1fb-e11faa51c052%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/537e0142-a726-44f8-a1fb-e11faa51c052%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/537e0142-a726-44f8-a1fb-e11faa51c052%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/537e0142-a726-44f8-a1fb-e11faa51c052%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](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+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHS2tHm2SkFZsVC77PGKASDxfTjfuzkJ\_21K-NW0WeEvg%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHS2tHm2SkFZsVC77PGKASDxfTjfuzkJ_21K-NW0WeEvg%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**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, 1:18am UTC](https://discuss.elastic.co/t/es-seems-slow-and-ineffecient/18391/5 "2017-07-06T01:18:54Z")

</div>


