![]() WPA lets you analyze this data to correlate across events and providers. Depending on how many types of events you are recording, you likely won’t even notice it running. When the issue comes up, I save the buffered events and dig in. Whenever I am trying to track down a performance issue, or even a hard to repro bug, I just start recording. WPR lets you continuously record the last (configurable-size) ETW events and some other types of information, including stack traces (sampling profiler) with very little impact to system performance. This is one of the 2 coolest tools I have learned to use this year (other: time travel debugging, which wpr/wpa overlap with a little in terms of use cases.) (Full disclosure: I work for Microsoft, not on this, and not for most of my career.)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |