# Elasticsearch search latency with young GC

**URL:** <https://discuss.elastic.co/t/elasticsearch-search-latency-with-young-gc/174897>\
**Category:** Elasticsearch\
**Created:** [April 2, 2019, 1:54am UTC](https://discuss.elastic.co/t/elasticsearch-search-latency-with-young-gc/174897 "2019-04-02T01:54:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hackerwin7](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hackerwin7/32/43223_2.png) [@hackerwin7](https://discuss.elastic.co/u/hackerwin7)\
**Post date:** [April 2, 2019, 1:54am UTC](https://discuss.elastic.co/t/elasticsearch-search-latency-with-young-gc/174897/1 "2019-04-02T01:54:47Z")

</div>

version is 6.5.1

When there is a frequently young GC occurred, the search latency raised to 200 ~ 500 ms, however the normal latency is within 100ms. all api is simple search api.

 ![54](https://us1.discourse-cdn.com/elastic/original/3X/4/0/401b6682b7e9b77bba80c4a556c7dc39c94f1600.png)

![18](https://us1.discourse-cdn.com/elastic/original/3X/a/4/a480056eaaae61f7047e2d8cf4018c38b58cd29e.png)

there is no even full GC, and the log have no any relatives info about gc, just print:

```
global ordinals took ...
global ordinals took ...
```

---

<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:** [April 30, 2019, 2:00am UTC](https://discuss.elastic.co/t/elasticsearch-search-latency-with-young-gc/174897/2 "2019-04-30T02:00:23Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.