# Real-time dashboards with direct query mode

**URL:** <https://community.amazonquick.com/t/real-time-dashboards-with-direct-query-mode/9733>\
**Category:** Q&A\
**Tags:** analysis, calculations, quick-sight\
**Created:** [February 6, 2023, 8:59am UTC](https://community.amazonquick.com/t/real-time-dashboards-with-direct-query-mode/9733 "2023-02-06T08:59:11Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![quser](https://avatars.discourse-cdn.com/v4/letter/q/ee7513/32.png) [@quser](https://community.amazonquick.com/u/quser)\
**Post date:** [February 6, 2023, 8:59am UTC](https://community.amazonquick.com/t/real-time-dashboards-with-direct-query-mode/9733/1 "2023-02-06T08:59:11Z")

</div>

I want to create a dashboard that shows fresh DynamoDB data that comes in real-time. Using direct query mode for the dataset, the concept worked for low number of incoming events.  
Now, having event rate at ~10 events / second, and after refreshing the dashboard just once, I need to wait for several minutes until I see the following on both of my visuals (a table and a bar chart:

 ![image](https://d1wl4jav5dp96l.cloudfront.net/original/2X/f/ff453584f01d6133c8538baa2201a4fa684e01f9.png)  
The total data at the time of making the screenshot should amount to 2-3k of events.  
What I would like to ask is:

1. how to make the data displayable on demand?
2. what are Quicksight DOs and DON’Ts when implementing this sort of semi-realtime dashboards?

---

<div class="post-metadata">

**Author:** ![Naveed](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/naveed/32/961_2.png) [@Naveed](https://community.amazonquick.com/u/Naveed)\
**Post date:** [February 6, 2023, 9:26am UTC](https://community.amazonquick.com/t/real-time-dashboards-with-direct-query-mode/9733/2 "2023-02-06T09:26:57Z")

</div>

Hi,

It all depend on your database configuration. How much time taking to respond QS.  
Filters are also the overhead on direct query. Every click generate a query for dB engine.

You can use the schedule refresh with minute work with 15 minimum. This feature available in Enterprise versions of QS.

Regards,  
Naveed Ali

---

<div class="post-metadata">

**Author:** ![quser](https://avatars.discourse-cdn.com/v4/letter/q/ee7513/32.png) [@quser](https://community.amazonquick.com/u/quser)\
**Post date:** [February 6, 2023, 9:54am UTC](https://community.amazonquick.com/t/real-time-dashboards-with-direct-query-mode/9733/3 "2023-02-06T09:54:17Z")

</div>

Thanks. The point, still, is to make data refreshes on-demand instead of scheduled. There are two filters applied.  
By database configuration, do you mean read throughput of the Dynamo table?

---

<div class="post-metadata">

**Author:** ![Naveed](https://d2orw1595917va.cloudfront.net/user_avatar/community.amazonquick.com/naveed/32/961_2.png) [@Naveed](https://community.amazonquick.com/u/Naveed)\
**Post date:** [February 6, 2023, 9:56am UTC](https://community.amazonquick.com/t/real-time-dashboards-with-direct-query-mode/9733/4 "2023-02-06T09:56:13Z")

</div>

database configuration means the hardware database is using. You need to check, what’s QS query took the CPU/RAM etc of your database server.