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:

Setting Description
MashupDefaultPoolContainerMaxCount Maximum container count for Power BI refresh, Azure Analysis Services, and others.
MashupDQPoolContainerMaxCount Maximum container count for Power BI Direct Query.
MashupDQPoolContainerMaxWorkingSetInMB Maximum working set size for Power BI Direct Query.
MashupTestConnectionPoolContainerMaxInstanceCount Maximum container count for test connections.
MashupAzureConnectorsCachingPoolContainerMaxCount Maximum container count for LogicApps, Power Apps, and Power Automate.
MashupAzureConnectorsCachingPoolContainerMaxWorkingSetInMB Maximum working set size for LogicApps, Power Apps, and Power Automate.

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, automatic scaling is not enabled by default. To enable it, in \Program Files\On-premises data gateway\Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config set MashupDisableContainerAutoConfig to False.