Forum Discussion
HELP! Microsoft Mashups are eating my memory
Ever since I updated to the new Report Server, my PBI server is getting killed by Mashups. It looks like they are not being released after use and just keep building up until I start to loose functionality. Paginated reports start getting 403 errors.
Eventually I stop and restart the Report server and that buys me another few hours.
8 processor and 24G memory. Used to be 12G and that was just fine.
10 Replies
You may look at this new article from Chris Webb and see if manipulating below 2 registry settings can help here!
ForegroundEvaluationContainerCount
MaxEvaluationWorkingSetInMB
Not sure how those are related to Report Server. As far as I can see, the problem is that the number of Mashups just keeps growing. Well betond the 20 that is mentioned in the article. I've seen as many as 50 or more. It's like it fires one up and then forgets it's there.
Here is what I get after less than an hour.
Measuring Power BI document memory consumption
While using Power BI desktop to create a Power BI report, you can use the Windows Task Manager to review the current memory footprint of the report. To do this:A. Open the report in Power BI Desktop
B. Insert a blank page
C. While in the blank page, save and close the report
D. If possible, close all open applications
E. Launch Power BI Desktop again, and open the previously saved report
F. Once the report is open, you should be in the blank page that you had added (the report should open to the blank page added in Step B, above)
G. Open Windows Task Manager by pressing Ctrl-Alt-Del, and selecting Task Manager from the list provided. Expand the Power BI Desktop Group under the process tab
(Detailed information about these processes can be found at the end of this post.)H. Wait for the report CPU % to approach zero, which means that it has completed loading it into memory. See this sample report on the blank page.
Hope You Find This Useful,
Peter
