Forum Discussion
Gateway issues
Right now I am using the gateway for report refresh in P1 capacity but it is getting slower because the number of reports has increased significantly. So I have decided to move to P3.
1) Do you think this solution will help me achieve some speed in refreshing the report ?
2) How does the machine configuration that is hosting the gateway will impact in the refresh rate?
Right now I have 8 core machine with memory 140000 MB.
3) Do I need to upgrade my machine also?
Thanks
Hi BishwaR ,
The reason for the slow refresh of reports is not actually related to the performance of the gateway.
When Premium capacity performance issues arise, a common first approach is to optimize or tune your solutions to restore acceptable response times. The rationale being to avoid purchasing additional Premium capacity unless justified.
When additional Premium capacity is required, there are two options described in the article below:
- Scale-up an existing Premium capacity
- Add a new Premium capacity
Here are a few reasons why reports are slow to refresh:
1.Insufficient capacity resources.
2.Inefficient report designs.
3.Dataset is slow, especially when reports have previously performed well.
4.High concurrent report usage.
The article Optimizing Premium capacities shows possible issues and ways to identify and handle them.
As for gateway:
Minimum requirements
- .NET Framework 4.7.2 (Gateway release December 2020 and earlier)
- .NET Framework 4.8 (Gateway release February 2021 and later)
- A 64-bit version of Windows 8 or a 64-bit version of Windows Server 2012 R2 with current TLS 1.2 and cipher suites
- 4 GB disk space for performance monitoring logs (in default configuration)
Recommended
- An 8-core CPU
- 8 GB of memory
- A 64-bit version of Windows Server 2012 R2 or later
- Solid-state drive (SSD) storage for spooling.
Hope it helps,
Community Support Team _ Caitlyn Yan
If this post helps then please consider Accept it as the solution to help the other members find it more quickly.
2 Replies
Hi BishwaR ,
The reason for the slow refresh of reports is not actually related to the performance of the gateway.
When Premium capacity performance issues arise, a common first approach is to optimize or tune your solutions to restore acceptable response times. The rationale being to avoid purchasing additional Premium capacity unless justified.
When additional Premium capacity is required, there are two options described in the article below:
- Scale-up an existing Premium capacity
- Add a new Premium capacity
Here are a few reasons why reports are slow to refresh:
1.Insufficient capacity resources.
2.Inefficient report designs.
3.Dataset is slow, especially when reports have previously performed well.
4.High concurrent report usage.
The article Optimizing Premium capacities shows possible issues and ways to identify and handle them.
As for gateway:
Minimum requirements
- .NET Framework 4.7.2 (Gateway release December 2020 and earlier)
- .NET Framework 4.8 (Gateway release February 2021 and later)
- A 64-bit version of Windows 8 or a 64-bit version of Windows Server 2012 R2 with current TLS 1.2 and cipher suites
- 4 GB disk space for performance monitoring logs (in default configuration)
Recommended
- An 8-core CPU
- 8 GB of memory
- A 64-bit version of Windows Server 2012 R2 or later
- Solid-state drive (SSD) storage for spooling.
Hope it helps,
Community Support Team _ Caitlyn Yan
If this post helps then please consider Accept it as the solution to help the other members find it more quickly.1. That has nothing to do with gateway performance. Work with your report developers to reduce the runtime of their longest running queries.
2. You need as many cores as you can get. 8 cores is a good start, 16 is better. Memory is not as critical, each core only uses about 2GB
3. define "my machine"
