QS CloudWatch Metrics

Q&A
,
1

Hello!

I’m searching for a clarity about two specific QS CloudWatch metrics - DashboardLoadTime and VisualLoadTime.

My main question is - which metric represents the real wait time for the user to interact with the dashboard? Is it the DashboardLoadTime or max(VisualLoadTime) across all the visualisations on the specific sheet?

I read that DashboardLoadTime includes not only loading the visualisations but also rendering layot, parameters, filters, etc - > so it’s the slowest visual + overhead. Can the user start interacting with the dashboard before everything is ready?

The reason I’m asking is that for the max(VisualLoadTime) we have around 1.5 min → the slowest visualisation takes 1.5min, while DashboardLoadTime varies from minimum 4mins and sometimes it happened that the load time was 16 mins:

  1. Does this mean the user waited from 4 mins and 16 mins for the dashboard to be fully ready or he waited for 1.5min (the slowest visualisation)?
  2. What could be the reason why DashboardLoadTime is that long, especially this 16 mins one? What are the recomendations to improve that?

Also, I saw the case where for a specific dashboard VisualLoadTime is present, but on that same date DashboardViewLoadTime is not present, how can it be?

For the context - dashboard is embedded, SPICE dataset is used, dashboard has 2 sheets with pivot tables only + a lot of caclulated fields.

Best regards,
Kseniya

2

Hi @ksenstad,

Hope this message finds you well! Based on this article discussing all of the metrics for Quick Sight, DashboardLoadTime looks like the determining factor representing full dashboard readiness and utilization capability. It is difficult to say conclusively why certain dashboards can take a while to load, but I would definitely look into this other article that mentions some common factors to long wait times and how to potentially mitigate those issues. Let me know if this helps!

3

Hi @ksenstad

It’s been a while since we last heard from you. If you have any further questions, please let us know how we can assist you.

If we don’t hear back within the next 3 business days, we’ll proceed with close/archive this topic.

Thank you!

4

Hi @ksenstad

Since we have not heard back from you, I’ll go ahead and close/archive this topic. However, if you have any additional questions, feel free to create a new topic in the community and link this discussion for relevant information.

Thank you!