Skip to main content
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

A new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.

pstewart1977

More success with personal gateway than on premises for refreshing reports without timeouts

Submitted by on ‎10-11-2017 08:38 AM

My VM with a low hardware spec is having more success refreshing a large report than the on premises data gateway when it comes to failed refreshes due to timeouts. The on premises data gateway has 8 cores and 8GB RAM the recommended microsoft spec. Will adding more performance spec to the gateway improve performance?

Status: New
See more ideas labeled with:
2 Comments (2 New)
Comments
v-haibl-msft
Microsoft Employee
Microsoft Employee
‎10-12-2017 11:10 PM

@pstewart1977

 

Are you using the same version of personal gateway and on-premises data gateway? Are you refreshing the same dataset with same queries? 

Do you force the gateway to use HTTPS traffic with Azure Service Bus instead of TCP? This will greatly reduce performance.

Please also disable the additional logging option since it will log verbose entries to the gateway which may impact the performance.

 

More success with personal gateway than on premises for refreshing reports without timeouts_1.jpg

 

The requirements listed here should be for both versions of gateway. And we also need to be aware that the network condition will also impact the gateway performance.

 

Best Regards,
Herbert

pstewart1977
Frequent Visitor
‎10-13-2017 12:51 AM

Cheers for the quick response Herbert. Both gateways are the same most recent version. TCP is ON. Debugging is off.

I think it's network related bottlenecks.

Idea Statuses