# The geo index and a million requests per second

**URL:** https://discuss.elastic.co/t/the-geo-index-and-a-million-requests-per-second/44648
**Category:** Elasticsearch
**Created:** [March 17, 2016, 5:55am UTC](https://discuss.elastic.co/t/the-geo-index-and-a-million-requests-per-second/44648 "2016-03-17T05:55:02Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![11114](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/11114/32/8524_2.png) [@11114](https://discuss.elastic.co/u/11114)
#### Post date: [March 17, 2016, 5:55am UTC](https://discuss.elastic.co/t/the-geo-index-and-a-million-requests-per-second/44648/1 "2016-03-17T05:55:02Z")

</div>

To Elastic, you can work with geo index fairly quickly.  
But I  
wouldn't want to write the data to disk and keep them in memory fast and  
moreover reliable. I have a query to update data every second and I  
need to find the closest route from the current position. Is it possible  
to set the ttl for the records. Thank you!

---

<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:07pm UTC](https://discuss.elastic.co/t/the-geo-index-and-a-million-requests-per-second/44648/2 "2017-07-05T23:07:40Z")

</div>