Don't miss your chance to take the Fabric Data Engineer (DP-700) exam on us!
Learn moreWe've captured the moments from FabCon & SQLCon that everyone is talking about, and we are bringing them to the community, live and on-demand. Starts on April 14th. Register now
Hello,
I work for a small startup where we operate on AWS, and I am the sole person responsible for data management where I present information using Power BI dashboards.
I chose to use the Import Mode to run scheduled refreshes because I've read that Direct Query tends to run slower on Power BI Service, and I want to ensure a smooth experience for the end-user.
Everything works well, but the challenge I'm facing is that I installed the Gateway on an AWS EC2 with an m5.2xlarge processor (I tried smaller processors before, but scheduled refreshes failed). However, this setup led to a cost of 500 USD for a month, which is unsustainable for us, especially given that it's only running the Gateway.
So my doubt is, How do you refresh Power BI dashboards in a more cost-effective manner?
Thank you in advance!
Here are some ways to refresh Power BI dashboards in a more cost-effective manner:
are you running refresh 24/7?
if not you can think to shut down vm when not in use or scale down vm when pick is down
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
| User | Count |
|---|---|
| 29 | |
| 23 | |
| 17 | |
| 15 | |
| 14 |