website loading slow, when the root directory is attached to Azure file share

Naveen naidu 5 Reputation points

I have a web application hosted on AKS, it takes its content from Azure file share, which is around 1GB, website takes time to load, like 60 to 70 seconds, we have provisioned premium storage, but no use

Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
2,774 questions
Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS)
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
1,903 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Sumarigo-MSFT 44,096 Reputation points Microsoft Employee

    @Naveen naidu Welcome to Microsoft Q&A Forum, Thank you for posting your query here! You are using Azure speed test tool to check the speed: am I correct ?

    There is no throttling on the Azure side, refer to below article. If the network and client machine can handle the traffic then we will send it. Here's a guide for troubleshooting high E2E latency:

    • Can you use a content delivery network (CDN) to cache static content and reduce the load on your web server.
    • Try to optimize your web application code and database queries to reduce the amount of data that needs to be transferred between the server and the client.

    Performance tuning for file servers Can you download PerfInsights tool, for Performance data collection Windows
    Using PerfInsights:

    • Execute PerfInsights using the Azure Files scenario: PerfInsights.exe /r azurefiles /sr 9971**9
    • Select Y to agree to share diagnostic information
    • Select Y to agree PerfInsights EULA.
    • Reproduce the performance issue or make sure that it's occurring.
    • When enough data is collected , press any key to stop diagnostic data collection.
    • Retrieve the compressed file created under the current folder with format similar to ""

    Additional information: Sometimes your proxies/VMs or whatever runs in the same datacenter, network requests does not leave the local network and the speed then depends on the infrastructure. (routers, firewalls, cables, etc). I'm sure they won't limit speed between their own infrastructure so services hosted on the same network works at full speed. There could be several reasons why your web application is taking a long time to load content from Azure file share. Here are a few things you can check:

    1. Network latency: Check the network latency between your AKS cluster and the Azure file share. You can use tools like ping or traceroute to diagnose network issues.
    2. Application performance: Check the performance of your web application. You can use tools like Azure Application Insights or Azure Monitor to monitor the performance of your application.
    3. AKS cluster performance: Check the performance of your AKS cluster. You can use tools like Azure Monitor for Containers or Kubernetes Dashboard to monitor the performance of your AKS cluster.
    4. File share caching: Consider using caching to improve the performance of the Azure file share. You can use tools like Azure Cache for Redis or Azure CDN to cache the content of the file share.

    If the issue still persist,  I would recommend you contact support, so If you have a support plan, I request you file a support ticket, else please do let us know, we will try and help you get a one-time free technical support. In this case, could you send an email to referencing this thread as well as your subscription ID. Please mention "ATTN subm" in the subject field. Thank you for your cooperation on this matter and look forward to your reply.

    I hope this helps you diagnose the issue. Let me know if you have any further questions!

    Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    0 comments No comments