Record a performance trace

If you are experiencing a problem with the performance of your Octopus installation we may ask you to record a performance trace and send the recording to us for analysis.

Performance analysis is most successful when you can provide us with a full picture of the problem at hand:

  • Recording of server metrics like CPU, RAM, Disk I/O and any other metrics which may be useful
  • Detailed Octopus logs.
  • The performance trace recording itself.


We use JetBrains dotTrace to record and analyze the performance trace. We are only concerned with which functions are called, how often they are called, and how long they take to execute. To protect your privacy we will provide you with a secure location to upload the recording, only use the recording for the performance analysis, and then delete all traces of the recording.

Getting prepared

  1. Download and install a trial of JetBrains dotTrace on your Octopus Server.
  2. Start recording CPU, RAM and Disk I/O using performance monitor (or similar).

Recording the performance trace

We don’t usually need a long recording, the most important thing is to get a recording of a short period of time where the problem occurs. This may be during a particular deployment, or when another Octopus task is running (like retention policy processing or health checks), or perhaps it’s just happening throughout the day.

If we haven’t asked for anything specific, start with a 1-5 minute recording so we can analyze it and go from there.

  1. Install dotTrace on the machine hosting Octopus Server.
  2. Start dotTrace as an Administrator and start a free trial (the trial can be paused after recording the trace).
  3. Start a timeline trace by attaching to the running Octopus Server process.
  4. When enough time has passed, take a snapshot using Get Snapshot'n'Wait.
  5. Detach from the process.
  6. Close dotTrace.
  7. Zip the dotTrace recording, the Octopus Server logs, Task Logs for tasks running during that period of time, and server metrics or a performance chart covering that period in time.
  8. Upload the zip file bundle to the secure and private share which should have been provided by an Octopus team member, then get back in touch with us - unfortunately we don’t get notified of file uploads.
  9. Pause the dotTrace trial when you’ve finished recording.


Due to the nature and depth of these investigations it may take a little while to analyze the performance trace and get to the bottom of what’s happening.

DIY performance analysis

We ship debugging symbols (PDB) files in the box with Octopus Server. This means you can use the dotTrace tooling to do your own analysis and understand exactly which functions could be causing the problem.

Help us continuously improve

Please let us know if you have any feedback about this page.

Send feedback

Page updated on Sunday, January 1, 2023