# Warmer API, high indexing rate, low index refresh interval

**URL:** <https://discuss.elastic.co/t/warmer-api-high-indexing-rate-low-index-refresh-interval/7897>\
**Category:** Elasticsearch\
**Created:** [May 29, 2012, 7:23pm UTC](https://discuss.elastic.co/t/warmer-api-high-indexing-rate-low-index-refresh-interval/7897 "2012-05-29T19:23:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![otisg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/otisg/32/492_2.png) [@otisg](https://discuss.elastic.co/u/otisg)\
**Post date:** [May 29, 2012, 7:23pm UTC](https://discuss.elastic.co/t/warmer-api-high-indexing-rate-low-index-refresh-interval/7897/1 "2012-05-29T19:23:39Z")

</div>

Hi,

Shay mentioned the following in another thread:

> In 0.20 we will have a warmer API that allows to pre-warm new segments,  
> meaning that search requests will not "suffer" loading the data.

Will the warmer help people who use low index refresh interval? Or should  
those people _not_ use the warmer?

For example, if I'm constantly indexing new docs and I have 1s refresh  
interval, if I were to use the new warmer I imagine ES might _constantly_  
be warming up new segments.  
I imagine that's not what one would want, right?  
ES may even not be able to keep up with the rate of new segment creation if  
document input rate is high?

## Thanks, Otis

Search Analytics - [Cloud Monitoring Tools & Services | Sematext](http://sematext.com/search-analytics/index.html)  
Scalable Performance Monitoring - [Sematext Monitoring | Infrastructure Monitoring Service](http://sematext.com/spm/index.html)

---

<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, 3:26am UTC](https://discuss.elastic.co/t/warmer-api-high-indexing-rate-low-index-refresh-interval/7897/2 "2017-07-06T03:26:29Z")

</div>