> I wish it were as easy to diagnose what consumes my IO on Windows. It seems like everything there runs as a thread in svchost, and > so I get no transparency into which program is to blame -- backup, AV, etc.
ProcessExplorer ( http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx) from the the SysInternals suite is exactly what you are looking for. The SysInternals apps make managing Windows boxes from the command line much less frustrating. JoshF On Wed, Jun 26, 2013 at 7:41 PM, Nicholas Leippe <[email protected]> wrote: > I've found dstat and htop handy. > > Also, lsof has been a lifesaver many times for me. > > Checking /proc/mdstat to see if a drive failed and it's rebuilding a hot > spare can help--but you should've got an alert for it already... > > /* > PLUG: http://plug.org, #utah on irc.freenode.net > Unsubscribe: http://plug.org/mailman/options/plug > Don't fear the penguin. > */ > /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
