Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Last time I used XPerf it killed my SSD, too much disk activity.
Is there an easy way to make XPerf write its trace data to an alternative hard drive?
I am using the script HeapMonitor.cmd to start up XPerf, so I am guessing there are some command line options for XPerf that will do what I need?
OK, so the answer is simply to move the HeapMonitor.cmd file to the other hard drive (non SSD) and it will just work.
There are command line options which look like this,
which could be changed to
I have done some of them, but not all of them, and it still seems to work.