# NGram Analyzer and Huge CPU Usage under 50 req/sec

**URL:** <https://discuss.elastic.co/t/ngram-analyzer-and-huge-cpu-usage-under-50-req-sec/32797>\
**Category:** Elasticsearch\
**Created:** [October 22, 2015, 6:01pm UTC](https://discuss.elastic.co/t/ngram-analyzer-and-huge-cpu-usage-under-50-req-sec/32797 "2015-10-22T18:01:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mehmet\_Cem\_Gunturkun](https://avatars.discourse-cdn.com/v4/letter/m/8491ac/32.png) [@Mehmet\_Cem\_Gunturkun](https://discuss.elastic.co/u/Mehmet_Cem_Gunturkun)\
**Post date:** [October 22, 2015, 6:01pm UTC](https://discuss.elastic.co/t/ngram-analyzer-and-huge-cpu-usage-under-50-req-sec/32797/1 "2015-10-22T18:01:17Z")

</div>

Hey everyone,  
I have some trouble with ngram analyzer and its cpu usage.  
The problem is I have two fields:

- one of them is analyzed by standard analyzer
- second is analyzed by standard analyzer and NGram filter.

When I run a load test with a query over the first field I can see 600 reqs/sec  
Same query over the other field only goes to 50 reqs/sec.

I create a detailed thread over stackoverflow, one of the users direct me to this forum. so I directly put the link of it:

> <https://stackoverflow.com/questions/33269595/elasticsearch-high-cpu-usage-during-load-test-50-req-sec>

I hope someone can give an advice about that because we need to give a decision before going to production with that schema.

Thanks.  
Mehmet -

---

<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 5, 2017, 11:43pm UTC](https://discuss.elastic.co/t/ngram-analyzer-and-huge-cpu-usage-under-50-req-sec/32797/2 "2017-07-05T23:43:09Z")

</div>

Closed on July 5, 2017, 11:43pm UTC