# ERROR: 'Getting data for this visualization took too long'

**URL:** <https://community.amazonquick.com/t/error-getting-data-for-this-visualization-took-too-long/14651>\
**Category:** Q&A\
**Tags:** performance, dashboard-performance, error, quick-sight\
**Created:** [June 14, 2023, 3:42pm UTC](https://community.amazonquick.com/t/error-getting-data-for-this-visualization-took-too-long/14651 "2023-06-14T15:42:41Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chirag\_Karkera](https://avatars.discourse-cdn.com/v4/letter/c/91b2a8/32.png) [@Chirag\_Karkera](https://community.amazonquick.com/u/Chirag_Karkera)\
**Post date:** [June 14, 2023, 3:42pm UTC](https://community.amazonquick.com/t/error-getting-data-for-this-visualization-took-too-long/14651/1 "2023-06-14T15:42:42Z")

</div>

I am seeing this error on many of my views in the dashboard. This error only occurs on a specific calculations which is of the form sum(avg(a, [b,c,d])).Is there a way to optimize this calculation? Also, the dataset is in SPICE but it is pretty large (500GB). Is there a way to partition the data to improve performance?  
 ![Screen Shot 2023-06-14 at 8.49.46 AM](https://d1wl4jav5dp96l.cloudfront.net/original/2X/f/f0a158ab32d15be0bae1cd505ea06daa8c5885e1.png)

---

<div class="post-metadata">

**Author:** ![Max](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/max/32/2288_2.png) [@Max](https://community.amazonquick.com/u/Max)\
**Post date:** [June 15, 2023, 2:26am UTC](https://community.amazonquick.com/t/error-getting-data-for-this-visualization-took-too-long/14651/2 "2023-06-15T02:26:10Z")

</div>

Hi @Chirag_Karkera

Can you move any of this logic to the query?

Maybe try and do an avg of a in a query to help save some compute.

---

<div class="post-metadata">

**Author:** ![Chirag\_Karkera](https://avatars.discourse-cdn.com/v4/letter/c/91b2a8/32.png) [@Chirag\_Karkera](https://community.amazonquick.com/u/Chirag_Karkera)\
**Post date:** [June 15, 2023, 4:02pm UTC](https://community.amazonquick.com/t/error-getting-data-for-this-visualization-took-too-long/14651/3 "2023-06-15T16:02:29Z")

</div>

Hi @Max  
Unfortunately, I can’t do that. Our dashboard needs both aggregated and unaggregated data in it. So I need to granular unaggregated data in the dataset. This enables me to aggregate data in views.

---

<div class="post-metadata">

**Author:** ![bergqdou](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/bergqdou/32/4265_2.png) [@bergqdou](https://community.amazonquick.com/u/bergqdou)\
**Post date:** [June 19, 2023, 10:51pm UTC](https://community.amazonquick.com/t/error-getting-data-for-this-visualization-took-too-long/14651/4 "2023-06-19T22:51:38Z")

</div>

Hi @Chirag_Karkera  
Maybe try using AvgOver() instead of avg(). Documentation below

> **[Using level-aware calculations in Amazon QuickSight - Amazon QuickSight](https://docs.aws.amazon.com/quicksight/latest/user/level-aware-calculations.html#level-aware-calculations-window)**
>
> Use level-aware calculations in an Amazon QuickSight analysis to insert a window or aggregate function into the order of evaluation.