Forum Discussion
New Power BI Embedded pricing model - page render
The response from the product team is
“page renders” are just a rough guideline, not an actual resource or limit. Therefore, it is not productive to get too detailed about what counts as a page render and what doesn’t.
The only limited resources in capacity are CPU, memory, and DirectQuery queries. Slicing, filtering, etc. will take up CPU and memory. If the dataset is DirectQuery, it will also take up DirectQuery queries.
First of all who ever made the comment "Therefore, it is not productive to get too detailed about what counts as a page render and what doesn’t." Does not understand it from customer perspective.
The reason we ask is because we need to know how to build our reports better. Though there is no limits, if we are on A1, and in a given day at our peak time of Noon, we hit the 300 page renders by 1215, then all other renders of the page will become slower, causing an impact to our customers and our brand.
So trying to better understand how page rendering works is very valuable as we do our design of application and our reports.
So please have the product team improve their answers.
Best Regards
asadhkhan That's a valid point.
Eric_Zhang Is there a guideline that says how to build our reports without causing slowness to the end users because of the limitation we setup on server? Do we have a best practice document? Even from a costing perspective for an organization with 1000+ dashboard users, how do we choose the plan? All of this can be done only if someone clearly defines the page renders. This question has not been answered for so many years and Microsoft Product Development team has a responsibility to respond to customers.
Regards
Jayashree
