Adjust gateway performance based on server CPU
The on-premises data gateway has settings that control resource usage on the machine where the gateway is installed. By default, gateway releases starting in June 2019 (3000.6.204) automatically scale these settings, using more or less resources depending on CPU capacity:
||Maximum container count for Power BI refresh, Azure Analysis Services, and others.|
||Maximum working set size for Power BI refresh, Azure Analysis Services, and others.|
||Maximum container count for Power BI Direct Query.|
||Maximum container count for test connections.|
||Maximum container count for LogicApps, Power Apps, and Power Automate.|
||Maximum container count for Power Query Online.|
MashupDefaultPoolContainerMaxWorkingSetInMB setting to change the default pool. Changing the memory set is only possible for the default pool. For the other pools, it isn't possible due to performance and stability reasons. The
MashupDQPoolContainerMaxWorkingSetInMB settings can't be changed in the config.
Most queries use mashup containers to execute. So the number of mashup containers determines the number of queries that can be executed in parallel. A working set defines the memory allocated to each container. These settings are available in \Program Files\On-premises data gateway\Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config.
If you've changed any of these settings manually, for these settings to take effect you must also disable automatic scaling by setting
MashupDisableContainerAutoConfig to True in \Program Files\On-premises data gateway\Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config. If
MashupDisableContainerAutoConfig is set to False, automatic scaling is always enabled.
Submit and view feedback for