# How to throttle analyzing (stemming, tokenizing, etc) **URL:** \ **Category:** Elasticsearch\ **Created:** [July 29, 2013, 7:50pm UTC](https://discuss.elastic.co/t/how-to-throttle-analyzing-stemming-tokenizing-etc/12990 "2013-07-29T19:50:45Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Bruno\_Miranda](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bruno_miranda/32/746_2.png) [@Bruno\_Miranda](https://discuss.elastic.co/u/Bruno_Miranda)\ **Post date:** [July 29, 2013, 7:50pm UTC](https://discuss.elastic.co/t/how-to-throttle-analyzing-stemming-tokenizing-etc/12990/1 "2013-07-29T19:50:45Z")
One one my indexes contains a lengthy text field that needs to be analyzed. During bulk index this causes the CPU of the ES instance to go to 100% utilization. Is there a way to throttle this process? -- 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). ---
**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:** [July 29, 2013, 10:52pm UTC](https://discuss.elastic.co/t/how-to-throttle-analyzing-stemming-tokenizing-etc/12990/2 "2013-07-29T22:52:07Z")
What is the analyzer of the field? Can you give an example of the lengthy text? Jörg On Mon, Jul 29, 2013 at 9:50 PM, Bruno Miranda [bru.miranda@gmail.com](mailto:bru.miranda@gmail.com)wrote: > One one my indexes contains a lengthy text field that needs to be > analyzed. During bulk index this causes the CPU of the ES instance to go to > 100% utilization. Is there a way to throttle this process? > > -- > 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). ---
**Author:** ![simonw\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simonw_2/32/1130_2.png) [@simonw\_2](https://discuss.elastic.co/u/simonw_2)\ **Post date:** [August 2, 2013, 8:15pm UTC](https://discuss.elastic.co/t/how-to-throttle-analyzing-stemming-tokenizing-etc/12990/3 "2013-08-02T20:15:11Z")
maybe send less docs in the bulk or dont' send the bulks concurrently? On Monday, July 29, 2013 9:50:45 PM UTC+2, Bruno Miranda wrote: > One one my indexes contains a lengthy text field that needs to be > analyzed. During bulk index this causes the CPU of the ES instance to go to > 100% utilization. Is there a way to throttle this process? -- 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). ---
**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:23am UTC](https://discuss.elastic.co/t/how-to-throttle-analyzing-stemming-tokenizing-etc/12990/4 "2017-07-06T02:23:11Z")