how to fix the VM uncached bandwith issue that is getting triggered again and again

To address the VM uncached bandwidth issue that is affecting your frontend application, consider the following steps:

1. Monitor Performance Metrics: Use Azure Monitor to check the performance metrics of your VM, especially focusing on the VM Cached IOPS, Uncached IOPS, and bandwidth consumed. This will help you identify if you're hitting the limits of your VM's capabilities.
2. Optimize Disk Configuration: Ensure that your disk configuration aligns with your workload requirements. Since you are using a Premium SSD, verify that the disk's performance capabilities are not being exceeded. You may need to consider resizing your disk or using multiple disks if necessary.
3. Scale Up the VM: If your application requires more resources than your current VM size can provide, consider scaling up to a larger VM size that offers higher uncached bandwidth and IOPS. The Standard E8as v4 may not be sufficient for your workload, especially if the application is latency-sensitive.
4. Check for Throttling: Investigate if there is any throttling occurring at the VM or disk level. You can refer to the Azure documentation for metrics that indicate whether your VM is being throttled due to exceeding IOPS or bandwidth limits.
5. Load Balancing: If your application can be distributed across multiple VMs, consider implementing load balancing to distribute the workload evenly, which can help mitigate bandwidth issues.
6. Review Application Performance: Sometimes, the issue may not solely be with the VM or disk but could also stem from how the application is designed. Review the application code and database queries to ensure they are optimized for performance.
7. Use Azure Premium Storage: If you are not already using Azure Premium Storage, migrating to it can provide better performance for your VM workloads, especially for I/O-intensive applications.

By following these steps, you should be able to address the uncached bandwidth issues and improve the performance of your frontend application.

References:

• Virtual machine uncached vs cached limits
• Troubleshoot Azure virtual machine performance on Linux or Windows

Hello @MEHRA, ANCHAL ,

Based on your description this seems more like your VM is not able to meet the performance which could be due to your application requirement for more resources with the VM but possible due to VM/disk usage you are not getting optimal performance.

Potential short-term fixes that you can try :

• Change disk caching to "ReadOnly" if mostly read operations
• Temporarily scale up to E16s v4 (384 MB/s uncached) to confirm if it improves the performance.

Long-term solutions for your VM:

• Upgrade to E16s v4 for higher uncached limits
• Consider Ultra Disks for guaranteed high throughput with low latency
• Implement application-level caching (Redis, Memcached)
• Configuration optimizations: -> Implement filesystem tuning appropriate for your workload -> Move logs/temp files to separate disk -> Adjust application logging levels to reduce disk writes

Do let me know if these help out to fix the issue for you.