# How to close ES automatic optmization which happens at UTC 0? **URL:** \ **Category:** Elasticsearch\ **Created:** [August 29, 2016, 6:22am UTC](https://discuss.elastic.co/t/how-to-close-es-automatic-optmization-which-happens-at-utc-0/59149 "2016-08-29T06:22:08Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![zehong\_yin](https://avatars.discourse-cdn.com/v4/letter/z/b3f665/32.png) [@zehong\_yin](https://discuss.elastic.co/u/zehong_yin)\ **Post date:** [August 29, 2016, 6:22am UTC](https://discuss.elastic.co/t/how-to-close-es-automatic-optmization-which-happens-at-utc-0/59149/1 "2016-08-29T06:22:08Z")
Hi, My ES 2.2 got a performance hit at UTC 0 (mid night). As far as I know, it seems triggered segments merging. In artical: [http://prog3.com/sbdm/blog/opensure/article/details/47617437](http://prog3.com/sbdm/blog/opensure/article/details/47617437) it menstioned: > Q4: stored into the Elasticsearch data, UTC is timestamp time,ElasticsearchCluster > will be at UTC 0 points, that is, Beijing time 8 points to > automatically perform optimization? How to change the parameter settings > for this time? > > We do not use the Elasticsearch automatic optimization settings. Own control optimization time. Is there anyone know how to disabel Elasticsearch automatic optimization settings? ---
**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\ **Post date:** [August 30, 2016, 6:57am UTC](https://discuss.elastic.co/t/how-to-close-es-automatic-optmization-which-happens-at-utc-0/59149/2 "2016-08-30T06:57:37Z")
Hi @zehong_yin, > [@zehong\_yin](#): > > My ES 2.2 got a performance hit at UTC 0 (mid night). What sort of performance hit did you experience exactly? Did indexing rate decrease? Did search latency increase? If yes, by what amount? How long did it last? What do your system metrics say for this time (CPU usage, memory usage, GC activity, network utilization...)? What was the load on your system at that time? Yes, Elasticsearch merges segments in the background _but_ the article gets this completely wrong. This does not happen at a specific time, but when the need arises. Read more about [segment merging in the Definitive Guide](https://www.elastic.co/guide/en/elasticsearch/guide/current/merge-process.html). You can also read there [what you can configure w.r.t. segment merging](https://www.elastic.co/guide/en/elasticsearch/guide/current/indexing-performance.html#segments-and-merging) _but_ please double and triple-check that this is really your issue (I doubt it). The quality of this article is questionable; I'd rather rely on what your system metrics tell you and then start [changing configuration in a scientifically controlled manner](https://www.elastic.co/guide/en/elasticsearch/guide/current/indexing-performance.html#_test_performance_scientifically). Daniel ---
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [August 30, 2016, 7:01am UTC](https://discuss.elastic.co/t/how-to-close-es-automatic-optmization-which-happens-at-utc-0/59149/3 "2016-08-30T07:01:29Z")
If you are using time-based indices, new indices will be created at or around midnight UTC, which requires a cluster state update. Are you using time-based indices? If so, how many indices do you have per day? ---
**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, 10:24pm UTC](https://discuss.elastic.co/t/how-to-close-es-automatic-optmization-which-happens-at-utc-0/59149/4 "2017-07-05T22:24:12Z")