![]() This is how we discovered it was Windows Update that bashed our disks. The "services" tab will highlight the services using that PID: To discover the actual service hiding behind it click "Go to services" If you see the "svchost" process among the top I/O consumers - it means the load is caused by some system service running behind this process. How do you tell which process is eating all the I/O? A simple way is to go to Task Manager - Details - Right-click the column headerts - Select Columns - Add "I/O read bytes" and "I/O write bytes". In AWS for example, once a disk drains all its "burst credits" it becomes really slow. If your cloud server is sluggish, but the CPU and memory load look normal, you're probably facing a disk bottleneck. So here are the steps we took to resolve it. The high load didn't stop after 1 hour, 2 hours, 5 hours. Yesterday, after routinely installing updates on one of our database servers (Windows Server 2016 running SQL Server), we faced an extremely high disk usage by the Windows Update service and its lieutenants - "TiWorker.exe" and the like. Resolving common server issues, handy tools reviews etc. Since most of our helpdesk customers are sysadmins we are starting a new series of posts in our blog - targeted specifically at server administratorss.
0 Comments
Leave a Reply. |