On-premises data gateway June 2019 update is now available
We are happy to announce that we have just released the June update for the On-premises data gateway (version 3000.6.202).
Here are some of the things that we would like to highlight with this month’s release:
- Performance Profile based on gateway CPU
- Port test Issue resolution
- HTTPS by default
- Gateway usage and Performance monitoring template update
Performance Profile based on gateway CPU
Currently the gateway application utilizes resources on your gateway machine based on preset configurations. Using this feature, the application can now scale to use more resources or less depending on the system CPU.
To allow the gateway to scale based on CPU, this configuration “MashupDisableContainerAutoConfig” would need to be “False”. When this is done, the following configurations are adjusted based on the gateway CPU.
The configurations in this section refer to containers and Working Sets. Most queries use mashup containers to execute. So, the number of mashup containers determine the number of queries which can be executed parallelly. A working set defines the memory allocated to each container. These configurations would be available in the Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file in the “\Program Files\On-premises data gateway” folder
- MashupDefaultPoolContainerMaxCount: Maximum container count used for Power BI Refresh, AAS 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 connection
- MashupTestConnectionPoolContainerMaxWorkingSetInMB: Maximum working set size for test connection
- MashupAzureConnectorsCachingPoolContainerMaxCount: Maximum container count for LogicApps, PowerApps, Flow
- MashupAzureConnectorsCachingPoolContainerMaxWorkingSetInMB: Maximum working set size for LogicApps, PowerApps, Flow
Note: This feature will automatically be implemented with the install or update of the June gateway if there have been no prior manual changes to the above configurations. In cases, where these configurations have been updated manually, to use this feature, you would need to explicitly set this configuration “MashupDisableContainerAutoConfig” to “False”.
- Port test Issue resolution: The port test on the On-premises data gateway application used to fail you were using a proxy. This issue has now been fixed.
- HTTPS by default –Starting with the June Gateway release, new installs (not updates) will default to HTTPS instead of TCP based on recommendations by the Azure Service Bus. If the gateway cannot connect using HTTPS, it will fall back to TCP/IP.
- Gateway usage and Performance monitoring template update – In May, we released the Gateway Usage and performance monitoring Hope you got a got a chance to use it. Based on your feedback,in this release, we fixed a couple of issues which caused the csv format of log files to be invalid. The issues are:
- Numerical columns having commas
- The error type with a line break
We have also updated the Gateway Performance PBI template file.
Do let us know if you have any additional feedback.
Please note that some of these upcoming changes may impact you:
We would be using .NET 4.7.2 framework for gateways July 2019 version or higher hence some of the operating systems we used to support may no longer be supported. More information about OS which will be supported here.
Please continue to send us feedback for what new capabilities you’d like to see in the future.