Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
Hello all,
Today we cut over to serve up our embedded reports via the Embedded V2 API accessing a Third Party Workspace application using the Azure SKU. We've been using V1 embedded for over a year and things have been swimmingly good.
Our V2 embedded site is failing miserably. We get reports to render fast and well for about 10 minutes then it just plain stalls...until some of the visuals time out even. That's at the A1 level...so we pushed it up to the A2 level to see if it was a resource issue. Same types of problems. Btw, we're talking only 1 user on the site at a time during this cutover period....so plenty of slicer clicks by the single user setting slicers or tabs....but 1 user.
Sometimes the visuals timeout on load and "X" out...same look as an expired token, but on initial load after 1 minute of not finishing a page load.
So we then also purchased a support plan...which is expensive as well for our single developer. And are waiting help.
In the meantime, I have no idea how to figure out if we're consuming a lot of A1 resource with a single user? Is the pricing model that wacky because of the way they count page renders? Any thoughts? We are lost.
Tom
Here's an example message.
Solved! Go to Solution.
As I experiment with how to work around this dreadful situation, let me recap:
As we look to manage our site...and manually scale capacity when people log on (we know that A1 will last about 15 minutes...very draggy tho) what I find is that during the scale up or down--the capacity basically shuts down altogether for about 1-2 minutes during this process--and the site fails.
Not sure what else to add. It's really a seriously grevious situation will pull us under.
You could say we've been warned...since we had some time to get it working...and we got it working and waited until now to cutover. What we never did was suspect that an A1 level was so anemic as to be unusable for a "made for powerbi" commercial application such as ours.
Like I've said before: don't believe me, let's share screens. The facts will reveal themselves quickly.
And as a rhetorical question, how can any commercial application bootstrap itself and have expenses grow with revenue when the smallest purchasable level of resource fails with one user on the site for more than 15 minutes?
Tom
Hi @ThomasDay,
I'm afraid this isn't an issue that others could have.
1. Did you need to migrate your contents? If so, did you do it properly? Please refer to migrate-from-powerbi-embedded.
2. Did you modify your application to use the Power BI REST API? Please refer to #rebuild-your-application.
If you can share the solution when you get it, I will appreciate it.
Best Regards,
Dale
@v-jiascu-msft thank you for your reply. Here's what I've discovered.
As I experiment with how to work around this dreadful situation, let me recap:
As we look to manage our site...and manually scale capacity when people log on (we know that A1 will last about 15 minutes...very draggy tho) what I find is that during the scale up or down--the capacity basically shuts down altogether for about 1-2 minutes during this process--and the site fails.
Not sure what else to add. It's really a seriously grevious situation will pull us under.
You could say we've been warned...since we had some time to get it working...and we got it working and waited until now to cutover. What we never did was suspect that an A1 level was so anemic as to be unusable for a "made for powerbi" commercial application such as ours.
Like I've said before: don't believe me, let's share screens. The facts will reveal themselves quickly.
And as a rhetorical question, how can any commercial application bootstrap itself and have expenses grow with revenue when the smallest purchasable level of resource fails with one user on the site for more than 15 minutes?
Tom
User | Count |
---|---|
18 | |
11 | |
5 | |
4 | |
3 |