On-premises gateway configuration

[Anonymous]

Hello all,

Currently I am reading about gateway configurations and I have 2 questions about it. The configurations that I am talking about is the one that can be checked by gateway admin in Microsoft.PowerBI.DataMovement. Pipeline.GatewayCore.dll.config file available in the Program Files\On-premises data gateway folder. 

The configurations:

1- CPUUtilizationPercentageThreshold  
2- MemoryUtilizationPercentageThreshold
3- ResourceUtilizationAggregationTimeInMinutes
4- ConcurrentOperationLimitPreview

The questions:

1- I am trying to find the best number to set for the configurations, and I only found one source of recommendation for this. I read on a blog that if you have 2 gateways, the author recommends to have one gateway runs at 100%. I wanted to confirm regarding this statement and maybe get more opinions on this.

2- I asked another person to check his gateway configuration (because I have no access to the file), and he said that he could not find "ConcurrentOperationLimitPreview". Does anyone knows why?

This might seem a lot, but thank you to anyone who are willing to help!

[v-yueyunzh-msft]

Hi,  @Anonymous 

The Microsoft.PowerBI.DataMovement.Pipeline.GatewayCore.dll.config file is a configuration file used to configure whether to send to a certain gateway during load balancing of the gateway cluster. If a gateway cluster with load balancing enabled receives a request from one of the cloud services (like Power BI), it randomly selects a gateway member. If this member gateway is already at or over one of the throttling limits specified below, another member within the cluster is selected. If all members within the cluster are in the same state, the request fails.

For the different paramter means you can refer to the official document:
Manage on-premises data gateway high-availability clusters and load balancing | Microsoft Learn

And for your second question, in my file it exists the "ConcurrentOperationLimitPreview".And this is just the configuration file , if it not exist , you can just use the text editor to add this paramter in this config file:

And you can also re-install the data gateway in your side and download the newest version .I think this configuration parameter will exist under normal installation conditions.

 

Thank you for your time and sharing, and thank you for your support and understanding of PowerBI! 

Best Regards,

Aniya Zhang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly

[Anonymous]

Hello @v-yueyunzh-msft ,

Thank you for your reply! I will try your recommendation for my second question, and also thank you for explaining about the configuration. However, I am asking about the best throttling limits for each parameter because it mentioned that we can set our own limits between 0-100.

For example, if we set the number for CPU Utilization to 100, then it means that it will throttle the refreshing on the server when the % CPU Utilization gets to 100%. I read somewhere that if we activate the load balancing with 2 gateway members for example, it is best to set the throttling limits to 100 on one gateway. But I only found one source for this and wanted to confirm if this is also supported by others.

[v-yueyunzh-msft · Accepted solution]

Hi， @Anonymous 

According to my understanding, when you configure two gateways as a cluster, you can indeed set the throttling limits to 100 on one gateway. Load balancing is to randomly send requests to your gateway. If one of your gateways exceeds 100% (and you configure throttling limits to 100), then subsequent requests will go to another gateway by default instead of going to Your CPU takes up a lot of gateways. My understanding is that it can be configured according to your actual CPU usage, such as 80-100.

Thank you for your time and sharing, and thank you for your support and understanding of PowerBI! 

Best Regards,

Aniya Zhang

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly