So the Dude (that’s me) has gone over how to collect xperf traces a few times now, but what do we do after we’ve collected a solid .etl file you may ask? Well, that’s what this post is all about. This is how the Dude does it. The Dude you see is listening to Simple… Continue reading The dude does xperf…
Tag: wpt
RunAsRadio.com spot
Look for the Dudes’ interview with Richard Campbell on RunAsRadio, where I get into a discussion on Slow Boot/Slow Logon scenarios, tools to use and common culprits. The spot appears on May the 18th! Links discussed on the interview are: http://social.technet.microsoft.com/wiki/contents/articles/10130.root-causes-for-slow-boots-and-logons-sbsl.aspx http://blogs.technet.com/b/yongrhee/archive/2012/02/19/list-of-performance-hotfixes-post-sp1-for-windows-7-sp1.aspx Thanks! Jeff Stokes
The Dude’s Greatest Hits
As requested by several customers, I’m putting up a list of tools I find useful in troubleshooting, etc… First up…. Data Gathering I use the following tools to gather data from systems. Each has its own place, much like a mechanic has many tools, so does the average engineer… PFE MPS Reports. I use these… Continue reading The Dude’s Greatest Hits
How to collect a netmon 3.4 and xperf kernel trace and stop when a problem occurs.
So at a customer location the following question was posed to me: “In our VDI environment, how do we capture trace information? How can we set a capture for the network and xperf the user can start (or logon script the start) and then give them a link to click when a random non-reproducible problem… Continue reading How to collect a netmon 3.4 and xperf kernel trace and stop when a problem occurs.
33 Seconds lost at boot…
Imagine you are an enterprise customer who has several thousand desktops that boot slow. Inordinately slow…slow enough that your user base resists requests to reboot them for patch cycle or power savings efforts or diagnostics. So imagine you do the right thing, you keep the BIOS and firmware up to date, you update drivers, you… Continue reading 33 Seconds lost at boot…