Forum Discussion
Unexpected Mashup Engine Containers constantly processing
Hi vvillama ,BIntelligence ,
Please check the offical document about the minimum requirements of Power BI Desktop.
https://docs.microsoft.com/en-us/power-bi/fundamentals/desktop-get-the-desktop#minimum-requirements
Minimum requirements
The following list provides the minimum requirements to run Power BI Desktop:
-
Windows 7 / Windows Server 2008 R2, or later
-
.NET 4.5
-
Internet Explorer 10 or later
-
Memory (RAM): At least 1 GB available, 1.5 GB or more recommended.
-
Display: At least 1440x900 or 1600x900 (16:9) recommended. Lower resolutions such as 1024x768 or 1280x800 aren't recommended, as certain controls (such as closing the startup screen) display beyond those resolutions.
-
Windows display settings: If you set your display settings to change the size of text, apps, and other items to more than 100%, you may not be able to see certain dialogs that you must interact with to continue using Power BI Desktop. If you encounter this issue, check your display settings in Windows by going to Settings > System > Display, and use the slider to return display settings to 100%.
-
CPU: 1 gigahertz (GHz) or faster 32-bit or 64-bit x86 processor recommended.
And refer to the topic below about Microsoft mashup evaluation container.
Best Regards,
Jay
Hi Anonymous ,
Thanks for your reply.
Regarding the minimum requirements, i'd say the computer i'm using is covering them.
Regarding the link about mashup engine you're providing, i apologize in advance, but i fail to see the connection with the issue discussed in this thread.
Just to summarize, the same set of queries, placed in two different pbix files with the same settings, are providing different behaviour: One file is triggering three mashup engine threads upon opening and the other one is not.
There may be a hidden setting in one of the files that is causing this, or there may be another explanation.
The point being that these three mashup engine threads have not been triggered on purpose by any action made by me, such as refreshing the model or editing a query through the transform data UI, cannot be killed through task manager, and are "sucking" precious computer resources which are degrading the overall interaction with the app, making any edit anywhere a pain.
The purpose of this post is to learn what's going on, why is it occurring and how can we prevent it from happening.
Thanks and kind regards,