# Increasing max\_buckets for specific Visualizations

**URL:** <https://discuss.elastic.co/t/increasing-max-buckets-for-specific-visualizations/187390>\
**Category:** Kibana\
**Created:** [June 25, 2019, 4:49pm UTC](https://discuss.elastic.co/t/increasing-max-buckets-for-specific-visualizations/187390 "2019-06-25T16:49:22Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![nickpeihl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nickpeihl/32/112622_2.png) [@nickpeihl](https://discuss.elastic.co/u/nickpeihl)\
**Post date:** [June 26, 2019, 3:40pm UTC](https://discuss.elastic.co/t/increasing-max-buckets-for-specific-visualizations/187390/4 "2019-06-26T15:40:04Z")

</div>

Elasticsearch sets a default limit of 10000 for the `search.max_buckets` setting. This can be changed, but it can also have a detrimental effect on the cluster, as you say if someone sends "killer queries".

Kibana has a default limit of 2000 for the max buckets in the Advanced Settings under Management. This is a conservative limit and can be set higher. But passing a lot of data around in the browser can be extremely resource intensive and cause browser hangups.

Perhaps we should try to optimize your visualization rather than change cluster settings. Which visualization are you using that needs so many buckets? Does it make sense to visualize that much data at one time? There is a limit to how much detail human eye can perceive.

---

_[View the full topic](https://discuss.elastic.co/t/increasing-max-buckets-for-specific-visualizations/187390)._