# Slow aggregation queries, only after data change (ES 2.3) **URL:** \ **Category:** Elasticsearch\ **Created:** [November 17, 2016, 1:41pm UTC](https://discuss.elastic.co/t/slow-aggregation-queries-only-after-data-change-es-2-3/66398 "2016-11-17T13:41:28Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![eperry](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/eperry/32/551_2.png) [@eperry](https://discuss.elastic.co/u/eperry)\ **Post date:** [November 18, 2016, 10:05pm UTC](https://discuss.elastic.co/t/slow-aggregation-queries-only-after-data-change-es-2-3/66398/7 "2016-11-18T22:05:45Z")
it helps a little but you have to look at the OS/Hardware at this point 24M records / 6 shards / 3 nodes = 1 million records each shard is searching. So, you will probably have some Load average and IO on each system that you should check as that will have the most impact on searchs The other is what your actual search is (Can you provide an example) but in general if your using lots of \* or doing \_all fields will slow you down Try reading this document before we go much further > **[Optimizing Elasticsearch Searches](https://www.elastic.co/blog/found-optimizing-elasticsearch-searches)** > > Elasticsearch can query, filter and aggregate in many ways. Often there are several ways to solve the same problem – and possibly with very different performance characteristics. This article will cover some important optimizations that can buy you a... --- _[View the full topic](https://discuss.elastic.co/t/slow-aggregation-queries-only-after-data-change-es-2-3/66398)._