On-premises gateway, setting DbConnectionPoolMaxSize against Oracle

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