Forum Discussion
Active OneDrive makes whole environment 'sluggish'
Analyze Resource Consumption:
PerfInsights: Consider using PerfInsights, a tool specifically designed for Azure VMs. It provides insights into Azure best practices, SQL best practices, I/O latency graphs, and detailed CPU and memory information.
Existing Tools: Utilize familiar performance troubleshooting tools like Perfmon or Procmon (similar to on-premises servers). These tools can help identify resource-intensive processes and bottlenecks.
Common Factors for High-CPU Situations:
Recent Code Changes or Deployments: Check if recent code changes or deployments (especially for apps like Internet Information Services, Microsoft SharePoint, or Microsoft SQL Server) are contributing to the high CPU usage.
Updates: Investigate whether recent OS-level updates or application-level cumulative updates might be causing the issue.
Query Optimization: For SQL Server and Oracle data tier applications, outdated indexes or inefficient query plans can lead to increased CPU consumption.
Azure VM-Specific Processes: Certain processes (e.g., RDAgent, Monitoring Agent, MMA agent, or Security client) specific to Azure VMs may cause high CPU usage.
Check VM Size and Storage:
Verify if the current VM size (D4s_v5) is sufficient for the workload. If both CPU usage and available memory are consistently high, consider upgrading to a larger VM size (e.g., D8s_v5) to better support your users’ needs.
Monitor and Optimize:
Continuously monitor resource utilization using Azure Monitor or other monitoring tools.
Optimize your application code, database queries, and indexing to reduce unnecessary resource consumption.
Review Extensions and Agents:
Ensure that any extensions or agents running on the VM (e.g., Monitoring Agent, MMA agent) are configured correctly and not causing excessive CPU load.
Remember that each environment is unique, so tailor your troubleshooting approach based on the specific characteristics of your client’s AVD setup. If the issue persists, consider reaching out to Azure support for further assistance.