Solved: On-premises gateway, setting DbConnectionPoolMaxSi...

Eric7 · ‎03-29-2021

Hi, the on-premises gateway does take quite a lot of simultaneous database connections against our Oracle database when we refresh a dataflow residing in the Power BI Service or in the PowerApps/Power platform. It looks like it consumes about the same amount as the number of tables in the dataflow. Is there any way to limit this? I have tried to set DbConnectionPoolMaxSize=4 (the default was 256 i believe) in the following file on the gateway server

C:\Program Files\On-premises data gateway\Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config

in sections

</setting>

</setting>

</setting>

But the gateway still consumes 9 connections simultaneously.

If we start several refreshes against Oracle at the same time, we may easily end up starving our main business critical application for database connections.

Anyone who has more knowledge about this?

-Is it possible to set the DbConnectionPoolMaxSize?

-Is there a minimum value not possible to go under?

-Is this the right place or the right setting?

Eirik

Eric7 · ‎05-25-2021

I got answer from one of the developers (I blieve):

"Hi, it looks like the rate limiting factor here is the number of connections that Oracle will accept.

One thing that you can do is change the properties in this file to limit the number of concurrent connections:

Adjust gateway performance based on server CPU | Microsoft Docs

Change MashupDisableContainerAutoConfig to true

Then change MashupDefaultPoolContainerMaxCount to 1

Then restart the gateway.

This mitigation is extremely NOT recommended, you will see a performance impact for all requests, however it will serve as a rate limiter for # of connections to oracle.

Thanks,

Sheldon"

I have tried MashupDefaultPoolContainerMaxCount = 4, which in our case seemed to give a good balance between number of db connections and performance.

Eirik

View solution in original post

lbendlin · ‎05-25-2021

That may only work if you have a single gateway and a single dataset and a single Oracle data source. The moment you use multiple gateway cluster members (as you should for BCP) and you have multiple Oracle data sources ( very likely) this becomes close to impossible to control. Better beef up your Oracle server.

Eric7 · ‎05-25-2021

I got answer from one of the developers (I blieve):

"Hi, it looks like the rate limiting factor here is the number of connections that Oracle will accept.

One thing that you can do is change the properties in this file to limit the number of concurrent connections:

Adjust gateway performance based on server CPU | Microsoft Docs

Change MashupDisableContainerAutoConfig to true

Then change MashupDefaultPoolContainerMaxCount to 1

Then restart the gateway.

This mitigation is extremely NOT recommended, you will see a performance impact for all requests, however it will serve as a rate limiter for # of connections to oracle.

Thanks,

Sheldon"

I have tried MashupDefaultPoolContainerMaxCount = 4, which in our case seemed to give a good balance between number of db connections and performance.

Eirik