# 0.90.2 performance problem with 5w msg/sec

**URL:** <https://discuss.elastic.co/t/0-90-2-performance-problem-with-5w-msg-sec/13083>\
**Category:** Elasticsearch\
**Created:** [August 6, 2013, 2:41am UTC](https://discuss.elastic.co/t/0-90-2-performance-problem-with-5w-msg-sec/13083 "2013-08-06T02:41:13Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![baniu\_yao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/baniu_yao/32/2168_2.png) [@baniu\_yao](https://discuss.elastic.co/u/baniu_yao)\
**Post date:** [August 6, 2013, 2:41am UTC](https://discuss.elastic.co/t/0-90-2-performance-problem-with-5w-msg-sec/13083/1 "2013-08-06T02:41:13Z")

</div>

hey guys,

I'm using elasticsearch 0.90.2 with 4 servers in a cluster.

_My parameters are below:_

shards: 16  
replicas: 0  
bootstrap.mlockall: true

index.merge.scheduler.max\_thread\_count: 15

threadpool:  
index:  
type: fixed  
size: 100  
queue\_size: 10000  
reject\_policy: caller

index.merge.policy.merge\_factor: 1000  
cache.memory.small\_buffer\_size: 5mb  
cache.memory.large\_buffer\_size: 50mb

_JVM is "-Xmx12g -Xms12g -Xmn6g"_  
\*  
\*  
_---------------------------------------------------------------_  
\*  
\*  
For our environment, every morning will met a peak time which hits about 5w  
msg/sec and the elasticsearch servers' io are 100%.

My question is: is my servers meet the bottleneck of performance? what  
actions can I take to improve performance without enlarge the cluster?

--  
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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Perry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/perry/32/2185_2.png) [@Perry](https://discuss.elastic.co/u/Perry)\
**Post date:** [August 7, 2013, 2:13am UTC](https://discuss.elastic.co/t/0-90-2-performance-problem-with-5w-msg-sec/13083/2 "2013-08-07T02:13:26Z")

</div>

by 5w you mean 50k?

On Tue, Aug 6, 2013 at 10:41 AM, 姚仁捷 [baniu.yao@gmail.com](mailto:baniu.yao@gmail.com) wrote:

> hey guys,
> 
> I'm using elasticsearch 0.90.2 with 4 servers in a cluster.
> 
> _My parameters are below:_
> 
> shards: 16  
> replicas: 0  
> bootstrap.mlockall: true
> 
> index.merge.scheduler.max\_thread\_count: 15
> 
> threadpool:  
> index:  
> type: fixed  
> size: 100  
> queue\_size: 10000  
> reject\_policy: caller
> 
> index.merge.policy.merge\_factor: 1000  
> cache.memory.small\_buffer\_size: 5mb  
> cache.memory.large\_buffer\_size: 50mb
> 
> _JVM is "-Xmx12g -Xms12g -Xmn6g"_  
> \*  
> \*  
> _---------------------------------------------------------------_  
> \*  
> \*  
> For our environment, every morning will met a peak time which hits about  
> 5w msg/sec and the elasticsearch servers' io are 100%.
> 
> My question is: is my servers meet the bottleneck of performance? what  
> actions can I take to improve performance without enlarge the cluster?
> 
> --  
> 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).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
Perry | 彭琪  
[http://pengqi.me](http://pengqi.me)

--  
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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![chenryn](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chenryn/32/44917_2.png) [@chenryn](https://discuss.elastic.co/u/chenryn)\
**Post date:** [August 7, 2013, 3:00am UTC](https://discuss.elastic.co/t/0-90-2-performance-problem-with-5w-msg-sec/13083/3 "2013-08-07T03:00:06Z")

</div>

yes，w(an)万 mean 10k in Chinese.

2013/8/7 Perry [perrywky@gmail.com](mailto:perrywky@gmail.com)

> by 5w you mean 50k?
> 
> On Tue, Aug 6, 2013 at 10:41 AM, 姚仁捷 [baniu.yao@gmail.com](mailto:baniu.yao@gmail.com) wrote:
> 
> > hey guys,
> > 
> > I'm using elasticsearch 0.90.2 with 4 servers in a cluster.
> > 
> > _My parameters are below:_
> > 
> > shards: 16  
> > replicas: 0  
> > bootstrap.mlockall: true
> > 
> > index.merge.scheduler.max\_thread\_count: 15
> > 
> > threadpool:  
> > index:  
> > type: fixed  
> > size: 100  
> > queue\_size: 10000  
> > reject\_policy: caller
> > 
> > index.merge.policy.merge\_factor: 1000  
> > cache.memory.small\_buffer\_size: 5mb  
> > cache.memory.large\_buffer\_size: 50mb
> > 
> > _JVM is "-Xmx12g -Xms12g -Xmn6g"_  
> > \*  
> > \*  
> > _---------------------------------------------------------------_  
> > \*  
> > \*  
> > For our environment, every morning will met a peak time which hits about  
> > 5w msg/sec and the elasticsearch servers' io are 100%.
> > 
> > My question is: is my servers meet the bottleneck of performance? what  
> > actions can I take to improve performance without enlarge the cluster?
> > 
> > --  
> > 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).  
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> Perry | 彭琪  
> [http://pengqi.me](http://pengqi.me)
> 
> --  
> 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).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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:** [August 7, 2013, 7:05am UTC](https://discuss.elastic.co/t/0-90-2-performance-problem-with-5w-msg-sec/13083/4 "2013-08-07T07:05:48Z")

</div>

Can you explain why you select

-Xmn6g  
index.merge.policy.merge\_factor: 1000  
index.merge.scheduler.max\_thread\_count: 15  
threadpool:  
index:  
type: fixed  
size: 100  
queue\_size: 10000  
reject\_policy: caller

Note, with the exceptional huge merge factor 1000, you easily run into  
heavy and long lasting I/O situations. With the threadpool enlargement, you  
put extra burden on the heap (max. 100 x 10000 docs is quite heavy). My  
reommendation is, run default thread pool, a merge factor of 20, and  
consider fast disks (SSD).

Jörg

--  
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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![baniu\_yao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/baniu_yao/32/2168_2.png) [@baniu\_yao](https://discuss.elastic.co/u/baniu_yao)\
**Post date:** [August 7, 2013, 3:15pm UTC](https://discuss.elastic.co/t/0-90-2-performance-problem-with-5w-msg-sec/13083/5 "2013-08-07T15:15:50Z")

</div>

yes, 1w=10k, exactly in Chinese:)

在 2013年8月7日星期三UTC+8上午11时00分06秒，chenlin rao写道：

> yes，w(an)万 mean 10k in Chinese.
> 
> 2013/8/7 Perry \<[perr...@gmail.com](mailto:perr...@gmail.com) \<javascript:\>\>
> 
> > by 5w you mean 50k?
> > 
> > On Tue, Aug 6, 2013 at 10:41 AM, 姚仁捷 \<[bani...@gmail.com](mailto:bani...@gmail.com) \<javascript:\>\>wrote:
> > 
> > > hey guys,
> > > 
> > > I'm using elasticsearch 0.90.2 with 4 servers in a cluster.
> > > 
> > > _My parameters are below:_
> > > 
> > > shards: 16  
> > > replicas: 0  
> > > bootstrap.mlockall: true
> > > 
> > > index.merge.scheduler.max\_thread\_count: 15
> > > 
> > > threadpool:  
> > > index:  
> > > type: fixed  
> > > size: 100  
> > > queue\_size: 10000  
> > > reject\_policy: caller
> > > 
> > > index.merge.policy.merge\_factor: 1000  
> > > cache.memory.small\_buffer\_size: 5mb  
> > > cache.memory.large\_buffer\_size: 50mb
> > > 
> > > _JVM is "-Xmx12g -Xms12g -Xmn6g"_  
> > > \*  
> > > \*  
> > > _---------------------------------------------------------------_  
> > > \*  
> > > \*  
> > > For our environment, every morning will met a peak time which hits about  
> > > 5w msg/sec and the elasticsearch servers' io are 100%.
> > > 
> > > My question is: is my servers meet the bottleneck of performance? what  
> > > actions can I take to improve performance without enlarge the cluster?
> > > 
> > > --  
> > > 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:\>.  
> > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > 
> > --  
> > Perry | 彭琪  
> > [http://pengqi.me](http://pengqi.me)
> > 
> > --  
> > 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:\>.  
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![baniu\_yao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/baniu_yao/32/2168_2.png) [@baniu\_yao](https://discuss.elastic.co/u/baniu_yao)\
**Post date:** [August 7, 2013, 3:19pm UTC](https://discuss.elastic.co/t/0-90-2-performance-problem-with-5w-msg-sec/13083/6 "2013-08-07T15:19:30Z")

</div>

hi jorg,

sorry for that i cannot spell your name correctly in my input method:)

this params is a suggestion from my colleague who is more familiar with  
lucene than me.

I've observed the docs is about 200million one day and my tuning goal is up  
to 1billion docs one day. I think disk io is the bottle-neck in the cluster  
and i'd like to add more server to the cluster.

在 2013年8月7日星期三UTC+8下午3时05分48秒，Jörg Prante写道：

> Can you explain why you select
> 
> -Xmn6g  
> index.merge.policy.merge\_factor: 1000  
> index.merge.scheduler.max\_thread\_count: 15  
> threadpool:  
> index:  
> type: fixed  
> size: 100  
> queue\_size: 10000  
> reject\_policy: caller
> 
> Note, with the exceptional huge merge factor 1000, you easily run into  
> heavy and long lasting I/O situations. With the threadpool enlargement, you  
> put extra burden on the heap (max. 100 x 10000 docs is quite heavy). My  
> reommendation is, run default thread pool, a merge factor of 20, and  
> consider fast disks (SSD).
> 
> Jörg

--  
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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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, 2:22am UTC](https://discuss.elastic.co/t/0-90-2-performance-problem-with-5w-msg-sec/13083/7 "2017-07-06T02:22:23Z")

</div>


