Sources

The source selection panel is where you select the source of performance data. It will look something like this:

Applications

The list contains currently running applications in yellow. Once you’ve instrumented your application it will be shown here on the top of the list. You can connect to the application and see it’s performance as it is running. The applications are enumerated from the network so you can even run your application on one machine and profile it on another.

Trace files

The list also contains previously saved traces in blue. You can save and load trace files so that you can inspect them later, compare them with a new trace or to send them to someone else. The trace files are stored in your user documents folder and can be deleted by right clicking them.

Importing

Sometimes you might want to open a trace generated in a different format. For example the Chromium trace format. By pressing the Import Trace button you can select the json file from which you want to import performance data.

Importing trace files is also useful when you need to generate a trace on a specific machine or when you have a user experiencing an unreproducable performance problem.

Sampler

Qumulus supports sampling in addition to instrumentation. Sampling allows you to do high level profiling without having to modify your application. To start a sampled session first press the Open Sampler button, this will open the sampler dialog:

From here you select the process you want to profile. The view is sorted by CPU Usage by default so that if your application is using up a lot of CPU it will be right near the top. Once you’ve selected your app, you can either GO to sample all of it’s threads (current and future ones), or press the Right arrow button on the right to go to thread selection.

Note

Some processes may be protected against debugger interactions. These processes are flagged as inapt and are hidden by default.

Thread Selection

The threads view shows all the threads in your application. It will automatically pick up the name you’ve given to your threads so that you can recognise them easily. This list is sorted by thread spawning order by default, and shows the thread’s last known location, cpu usage and name. Select the threads you’re interested in, decide if you want recursions to be folded or not and press GO! From there you’re back into the main UI again where everything works as you would expect.

Example

The Launch Example / Stop Example button allows you to run the example application supplied with the QuSDK. This enables you to see what the code shared here generates and how that’s being shown in the timeline.