# Using elasticsearch as a cache with frequent updates

**URL:** <https://discuss.elastic.co/t/using-elasticsearch-as-a-cache-with-frequent-updates/34733>\
**Category:** Elasticsearch\
**Created:** [November 16, 2015, 9:10pm UTC](https://discuss.elastic.co/t/using-elasticsearch-as-a-cache-with-frequent-updates/34733 "2015-11-16T21:10:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lior](https://avatars.discourse-cdn.com/v4/letter/l/3ec8ea/32.png) [@Lior](https://discuss.elastic.co/u/Lior)\
**Post date:** [November 16, 2015, 9:10pm UTC](https://discuss.elastic.co/t/using-elasticsearch-as-a-cache-with-frequent-updates/34733/1 "2015-11-16T21:10:33Z")

</div>

We are considering to use ES as a cache, for storing about 100K documents and updating them every 1 minute.  
The size of each document is very small, containing 10-20 text fields.

We would like to know whether ES can support such an update scenario.  
Should we worry about memory fragmentation over time, resulting in performance deterioration, assuming that the volume of updates supersedes the volume of searches by a big order of magnitude?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [November 16, 2015, 9:32pm UTC](https://discuss.elastic.co/t/using-elasticsearch-as-a-cache-with-frequent-updates/34733/2 "2015-11-16T21:32:18Z")

</div>

I would probably use 2 indices and an alias.

Index in the cold index, switch the alias,  
delete the new cold index.

---

<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:38pm UTC](https://discuss.elastic.co/t/using-elasticsearch-as-a-cache-with-frequent-updates/34733/3 "2017-07-05T23:38:08Z")

</div>