# Aggregation profiling? **URL:** \ **Category:** Elasticsearch\ **Created:** [May 25, 2015, 9:08pm UTC](https://discuss.elastic.co/t/aggregation-profiling/23684 "2015-05-25T21:08:42Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![msukmanowsky](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/msukmanowsky/32/44771_2.png) [@msukmanowsky](https://discuss.elastic.co/u/msukmanowsky)\ **Post date:** [May 25, 2015, 9:08pm UTC](https://discuss.elastic.co/t/aggregation-profiling/23684/1 "2015-05-25T21:08:42Z")
I don't believe there are any current endpoints in the API that support this, but are there plans to add better profiling information to ES aggregation queries? We'll see some agg queries return in 11s, then \<5s then \>11s again. Sometimes we can see associated filter cache expirations, but it's really hard to line these up to one specific query in our production environment since multiple users are executing queries simultaneously. It'd be really helpful to optionally see where aggregation queries are spending the bulk of their time to help us understand what to improve in the future. Anything we can do here right now? -- Mike Sukmanowsky Aspiring Digital Carpenter _e_: [mike.sukmanowsky@gmail.com](mailto:mike.sukmanowsky@gmail.com) facebook [http://facebook.com/mike.sukmanowsky](http://facebook.com/mike.sukmanowsky) | twitter [http://twitter.com/msukmanowsky](http://twitter.com/msukmanowsky) | LinkedIn [http://www.linkedin.com/profile/view?id=10897143](http://www.linkedin.com/profile/view?id=10897143) | github [https://github.com/msukmanowsky](https://github.com/msukmanowsky) ## -- Please update your bookmarks! We have moved to [https://discuss.elastic.co/](https://discuss.elastic.co/) You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAOH6cu5WSGqQ%2BZ0\_qrofXEvwo8JuSH9xoSbZgSwiT90MJ\_wxdA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAOH6cu5WSGqQ%2BZ0_qrofXEvwo8JuSH9xoSbZgSwiT90MJ_wxdA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![James\_Macdonald](https://avatars.discourse-cdn.com/v4/letter/j/f19dbf/32.png) [@James\_Macdonald](https://discuss.elastic.co/u/James_Macdonald)\ **Post date:** [May 29, 2015, 3:43am UTC](https://discuss.elastic.co/t/aggregation-profiling/23684/2 "2015-05-29T03:43:16Z")
I don't have an answer, but I really like this question. I too would love to see more query and aggregation profiling tools for performance optimization purposes. Also, I assume you have already looked at this, but have you made sure you are not evicting anything from your in memory field data? James On Mon, May 25, 2015 at 4:08 PM, Mike Sukmanowsky \< [mike.sukmanowsky@gmail.com](mailto:mike.sukmanowsky@gmail.com)\> wrote: > I don't believe there are any current endpoints in the API that support > this, but are there plans to add better profiling information to ES > aggregation queries? We'll see some agg queries return in 11s, then \<5s > then \>11s again. Sometimes we can see associated filter cache expirations, > but it's really hard to line these up to one specific query in our > production environment since multiple users are executing queries > simultaneously. > > It'd be really helpful to optionally see where aggregation queries are > spending the bulk of their time to help us understand what to improve in > the future. > > Anything we can do here right now? > > -- > Mike Sukmanowsky > Aspiring Digital Carpenter > > _e_: [mike.sukmanowsky@gmail.com](mailto:mike.sukmanowsky@gmail.com) > > facebook [http://facebook.com/mike.sukmanowsky](http://facebook.com/mike.sukmanowsky) | twitter > [http://twitter.com/msukmanowsky](http://twitter.com/msukmanowsky) | LinkedIn > [http://www.linkedin.com/profile/view?id=10897143](http://www.linkedin.com/profile/view?id=10897143) | github > [https://github.com/msukmanowsky](https://github.com/msukmanowsky) > > ## -- Please update your bookmarks! We have moved to [https://discuss.elastic.co/](https://discuss.elastic.co/) > > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CAOH6cu5WSGqQ%2BZ0\_qrofXEvwo8JuSH9xoSbZgSwiT90MJ\_wxdA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAOH6cu5WSGqQ%2BZ0_qrofXEvwo8JuSH9xoSbZgSwiT90MJ_wxdA%40mail.gmail.com) > [https://groups.google.com/d/msgid/elasticsearch/CAOH6cu5WSGqQ%2BZ0\_qrofXEvwo8JuSH9xoSbZgSwiT90MJ\_wxdA%40mail.gmail.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/CAOH6cu5WSGqQ%2BZ0_qrofXEvwo8JuSH9xoSbZgSwiT90MJ_wxdA%40mail.gmail.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ## -- Please update your bookmarks! We have moved to [https://discuss.elastic.co/](https://discuss.elastic.co/) You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAABsnTZOmx-fk%2BG9dR6-XYB\_1j7mGRNRwTqvQRwKx0YAcopFWA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAABsnTZOmx-fk%2BG9dR6-XYB_1j7mGRNRwTqvQRwKx0YAcopFWA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**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, 12:10am UTC](https://discuss.elastic.co/t/aggregation-profiling/23684/3 "2017-07-06T00:10:58Z")