Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
Hello,
Desktop implementations of Power Query (e.g. Power BI Desktop, Excel) use a persistent cache that, in some cases, caches the data sent back in reply to queries/requests sent to external data sources.
IIRC, I've seen a few indications that the Power BI Service also has this kind of persistent cache.
Questions 🙂
(For clarity, the caching referred to above is not at the report level, so is different from what's described in Query caching in Power BI Premium.)
Thank you,
Ben
Solved! Go to Solution.
Yes, a persistent cache is used when refreshing queries in the PBI Service. However, the Service caching is slightly different than what happens when refreshing in Desktop. The primary difference is that in Desktop refresh, a single cache is shared by all the queries being refreshed. But in Service refresh, each query gets its own persistent cache. This can lead to Service refresh being slower than Desktop refresh, if the queries benefit from using the results cached by other queries in the dataset.
Hi @Ben-Dev ,
As far as I know it seems not similar persistent cache in Power BI Service.
Perhaps you can refer this thread that replied by Ehren:
How do I cache or buffer an intermediate query result for repeated
Best Regards,
Community Support Team _ Yingjie Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
@Ehren, can you offer any insight here? When Power Query runs in the Power BI Service, is a persistent cache used (e.g. same as what happens in Power BI Desktop and Excel)?
Yes, a persistent cache is used when refreshing queries in the PBI Service. However, the Service caching is slightly different than what happens when refreshing in Desktop. The primary difference is that in Desktop refresh, a single cache is shared by all the queries being refreshed. But in Service refresh, each query gets its own persistent cache. This can lead to Service refresh being slower than Desktop refresh, if the queries benefit from using the results cached by other queries in the dataset.
Thanks, @lbendlin! Actually, I'm referring to the external query caching that Power Query can do when loading data before it is in the dataset (so is different from whether or not the dataset is currently in memory).
I don't think that's a thing, unless I misunderstand what you're trying to figure out.
Datasets are loaded into the capacity memory. That's the equivalent of your "cache", but it's also fundamentally how the Power BI service works.
Either your dataset is in memory, or it isn't (when it has been evicted due to inactivity).
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Check out the January 2025 Power BI update to learn about new features in Reporting, Modeling, and Data Connectivity.