: Are there any plans for caching stat results for a certain stat field along : with the documents that match a filter query ? Any other ideas that could : help to improve this (hardware/software configuration) ? Even for a subset : of 10M entries, the stat search takes on the order of 10 seconds.
I don't know of anyone working on it, and off the top of my head i don't remember seeing any jira issues for it, but it certianly seems feasible to add optional caching (the StatsComponent could have an optional init param naming a user declared cache) Feel free to open a jira issue. -Hoss
