Hi Mazurek, Jakub,
Thanks for the question and using MS Q&A platform.
To address the high latency issues observed after transitioning to Premium-ZRS-FileStorage,
To make sure that your App Service plan has sufficient resources (such as CPU and memory) for the app you are trying to deploy. If you are on a premium plan and are still experiencing lag, consider scaling up or increasing the number of instances to handle the load. Monitoring CPU and memory usage can also be done with the App Service diagnostics to identify any resource bottlenecks. methods on App Service enable diagnostic logs to gain insights into how the app is performing.
They are particularly useful for tracing requests and dependencies that are taking too long through Azure Application Insights. Try determining what is causing the problem through the Application Insights Profiler, which helps in analyzing how the application performs at the code level.
Make sure to consider the network latency. The location of the App Service and these resources should ideally be in the same region to avoid unnecessary delays. Also, VNET integration might be something that adds some additional latency, so pay attention there too.
To reduce latency, consider an upgrade when serving static content from Premium-ZRS-FileStorage to Standard-ZRS-BlobStorage. Also, do not forget to check the IOPs and throughput limits on your storage ac.
Let me know if you have any assistances.
If the answer is helpful, please click Accept Answer and kindly upvote it so that other people who faces similar issue may get benefitted from it.
https://learn.microsoft.com/en-us/azure/app-service/troubleshoot-performance-degradation
https://learn.microsoft.com/en-us/troubleshoot/azure/azure-storage/blobs/alerts/troubleshoot-storage-performance#metrics-show-low-successe2elatency-and-low-successserverlatency-but-the-client-is-experiencing-high-latency