# Script result caching/reusing

**URL:** <https://discuss.elastic.co/t/script-result-caching-reusing/60042>\
**Category:** Elasticsearch\
**Created:** [September 8, 2016, 6:24am UTC](https://discuss.elastic.co/t/script-result-caching-reusing/60042 "2016-09-08T06:24:23Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![dmitry\_polushkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dmitry_polushkin/32/1326_2.png) [@dmitry\_polushkin](https://discuss.elastic.co/u/dmitry_polushkin)\
**Post date:** [September 24, 2016, 9:43am UTC](https://discuss.elastic.co/t/script-result-caching-reusing/60042/2 "2016-09-24T09:43:48Z")

</div>

I had almost the same questions recently. I don't know where to find any help with such use-case, but at least I understood there are no solutions in ES at the moment to optimize requests for the large index with many documents, especially if you have many aggs, filters and sort. I'd say the best thing could be done is to write to the github issues: [https://github.com/elastic/elasticsearch/issues/10767](https://github.com/elastic/elasticsearch/issues/10767) and [https://github.com/elastic/elasticsearch/issues/20131](https://github.com/elastic/elasticsearch/issues/20131)

My question is also uncommented: [Generate multiple scripted fields for the whole index to filter and aggregate](https://discuss.elastic.co/t/generate-multiple-scripted-fields-for-the-whole-index-to-filter-and-aggregate/58795)

Looks like here is nobody help anyone, at least for the complex questions, where the documentation cannot help.

---

_[View the full topic](https://discuss.elastic.co/t/script-result-caching-reusing/60042)._