Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
Dear Microsoft
[Firstly, apologies for posting this here; ideally I’d like to raise a support ticket but unfortunately my business PBI licence is currently on a Pro trial (until we complete a pilot/test phase before we formally procure PBI and integrate it into the business), so this is the next best step]
I am emailing to inform you of an on-going performance issue with Power BI Services that is unfortunately a serious ‘blocker’ in the progression of the BI ‘self-service’ project I am working on.
When using the PBI Services web portal to view and explore the visualisations, it’s commonly taking 45-90seconds for the visuals on any of the numerous visualizations I’ve created and deployed to PBI Services to successful update (and to stop showing the “spinning round clock”). For the same ‘performance issue’ to happen whenever we’re clicking on any one of the slicers, this unfortunately isn’t useable as a business solution in it’s current condition.
This issue has been going on for a few weeks now, and it’s preventing the initial procurement of 8 new PBI Pro licenses until the issue is resolved.
Some background & context
NOTE: Within our PBI Services account, the ‘Customer Ops’ workspace contains the visualizations that are intended for business use.
Some ideas on potential causes of the issue
NB: When using one of the Power BI Desktop files that was used to create the visualisation published to the PBI Service, with connectivity using only the one connection to our PBI Service dataset (mentioned above), this results in much better performance.
The reality
Our PBI account I speak of is current using a trial Pro licence. We are initially looking at purchasing eight PBI Pro licences. However, I first need to get ‘buy-in’ from senior management; I am currently holding back on giving a presentation on the ‘self-service’ solution show-casing the value of Power BI Services/Online, however, I am not willing to present a solution that so clearly isn’t fit for use.
Microsoft have been generous enough to provide me with an extended one year trial Pro licence (circa 4 months remaining). This has enabled me to further develop the BI solution and continue testing ready for business ‘buy-in’.
Any insight & assistance you could provide what be much appreciated.
Kind regards
Richard Nunn MCSA
Solved! Go to Solution.
Hello
Firstly, my sincere apologies for the dramatic delay in response; there’s been a number of altercations over the past few months, one is that I’m moving on to pastures new in a few weeks. That said, I’ve been meaning to respond to this post to provide my input & responses to the above for several weeks now(!).
Thank you for your response; I skimmed over the insightful Microsoft doc you referred me too and was happy to read that I was following industry ‘best practices’ (except for using PBIs platform to replicate the functionality of SSAS in the absence of SSAS teck) in the overall BI implementation/solution. The (other) exception was the ‘network latency’ section; this very well could have been a strong factor in this performance issue, it has always been a serious concern of mine here and had flagged internally. Unfortunately, this matter remains inconclusive.
Thank you for your response; correct, quite a few. However, as mentioned in my original post was the fact that, due to office circumstances at the time, SSAS teck was NOT being implemented. As I’m sure you know, SSAS is a teck that enables ‘performance tuning’ within its feature-set; since my original post, now that I’ve built, deployed and handling the data processing of the BI solution exclusively in SSAS (once I’d introduced the teck into the office), performance is now “user friendly” as you might expect. Ultimately, just as some offices might “incorrectly” use Excel as a ‘flat file database system’ in a way that the Excel teck isn’t explicitly designed for, PBI was also being used in a way that it isn’t explicitly designed for, and you get ‘real-world’ problems as you might expect.
Thanks all. I am happy for this post to be closed.