Gateway Bandwidth Requirement

[Arun_Prasath]

Hi Team,

When we talk about the bandwidth throughlting requirement between On-Premise Gateway and Power BI service, I see one single line "Strive for reliability, fast speeds, and low, consistent latencies" in this sizing document  This is not sufficient for architects to plan the right architecture.

Could we have an understanding on how much acceptable bandwidth is required when we deal with large query outputs. In other words , how Gateway will handle, if the bandwidth is very thin , will this affect the performance , when a refresh is done on dashboards ? 

[v-deddai1-msft]

Hi @Arun_Prasath ,

Thin bandwidth and network latency can impact report performance by increasing the time required for requests to reach the Power BI service, and for responses to be delivered. Tenants in Power BI are assigned to a specific region.

When users from a tenant access the Power BI service, their requests always route to this region. As requests reach the Power BI service, the service may then send additional requests—for example, to the underlying data source, or a data gateway—which are also subject to network latency and bandwidth .

Tools such as Azure Speed Test provide an indication of network latency between the client and the Azure region. In general, to minimize the impact of network latency, strive to keep data sources, gateways, and your Power BI cluster as close as possible. Preferably, they reside within the same region. If network latency is an issue, try locating gateways and data sources closer to your Power BI cluster by placing them inside cloud-hosted virtual machines.

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

Best Regards,

Dedmon Dai