Power Query - cache shared nodes
Update Power Query in Excel to take advantage of caching in cases where a parent node refers to a child node that has already been refreshed (as exists in Power BI desktop today).
This issue creates significant performance problems with refresh times when creating highly interdependent financial and operational models. This is a show stopper from a usability and customer acceptance standpoint.
We are happy to announce that the feature is finally available on Production starting from July fork (build 16.0.10726.*) for Office 365 subscribers.
Thank you all for your votes and the feedback.
- Excel Team
Josh Blackman commented
I completely agree with Ken Puls’ comment on 20 July 2017. When I posted the idea I didn’t understand the full scope of the problem and defined the issue way too narrowly. Please fix any and all issues affecting the performance of Power Query and Power Pivot refresh times (seek and destroy mission).
Request to the site admin, please change the name of the idea: Make Power Query (Get Data) faster!!!
This is the biggest issue I have in my day to day work. Not the biggest Excel issue, not the biggest IT issue, the single largest issue I have in being productive and delivering meaningful results for my business. Please help us, give us a better sword to slay the dragons. Priority up and lets do this!
Wyn Hopkins commented
Adding my strong endorsement of Ken and Imke's view
Imke Feldmann commented
Very much agree to @Ken Puls: We need performance improvements ... wherever they come from.
Ken Puls commented
One thing I wish we could do is rename this to "improve performance in Power Query", and not just limit this to the scope of one issue. This particular one is a problem, for sure, but there are many others, like this one http://www.thebiccountant.com/2017/07/20/sql-query-folding-bug-still-alive-sucking-powerbi-powerquery-excel/
Right now we need a considerable focus put on improving performance anywhere and everywhere it can be improved. I think many of the comments on this thread to date are made with this view in mind, but wanted to vocalize it myself.
Please please please. I have lots of reports I need Power Query to feed and they just are feasible because they are dreadfully slow to upload.
Justin Mannhardt commented
Agreed, much needed. Seconds matter, priority up!
using work around because of speed, amazing tool but users feel frustrated when they have to walk away and wait for querys to cycle.
Gerald Hinrichs commented
This is a "gotta have".
"One small step for man" - what else can we all say/do to encourage you guys?
Imke Feldmann commented
Dear Excel Team,
as far as I can see, this issue is on 3rd rank in Excel for Windows and on 7th rank in Excel over all. Wondering how much more we need to overcome the priority-threshold here?
Thx - Imke
Please fix PowerQuery refresh latency issues, thank you
This is my biggest challenge using PQ and an impediment to getting others in my organization on the PQ bandwagon. Please fix.
Top priority please
Lenny W. commented
Kindly fix the PQ slow refreshing issue.
Jes Hansen commented
Power Query + Power pivot in Excel = Great show starter
Slow refreshing in PQ + crashing in PP = Bad show stopper
Customers are actively rejecting the PQ + PP combination because of this and since some investment has already been allocated in the process before realizing the facts some badwill is returned towards Micorsoft and the consultants involved. A sound ROI would be much better for all those involved. PLEASE FIX THIS
PQ is an amazing tool and has revolutionised financial modelling within our organisation. However, we have had to stop using PQ solutions due to the refresh speed. This needs to be fixed urgently.
Tommy Jørgensen commented
Biggest issue with Power Query. #1 priority.
Top priority. Slow refresh times are a big problem.