Organizing the performance data

Sessions and Activities

An Activity must be created for every performance run. Existing Activities may be cloned (duplicated) to avoid creating one from scratch every time.

Here are some guidelines for when to create a new Session:
  • Each Session is associated with a runtime host. If you would like to profile your application on several machines you must create a Session for each one.
  • Another strategy for when to create a new Session is when you will be performance tuning your application under a set of criteria that makes the Activities in that Session not comparable to Activities in other Sessions. Some cases where this could happen is if you are using a significantly different set of inputs or if a long amount of time has passed and the application's behavior has changed.

Focusing on one Session at a time

The Performance Explorer can be focused on one project or Session at a time.

Right click a Session and select Go Into. This will cause the Performance Explorer to only display the Activities for that Session.

Use the browser-style navigation buttons in the Performance Explorer view toolbar to go back to viewing the entire workspace.

Archiving Activities

Select one or more Activities, right click, and select Archive.

This will move the Activities under the Archive node. The Archive node is collapsed by default in order to hide the archived Activites.

No actions can be performed on an archived Activity. To restore an archived Activity right click it and select Restore. This will move the Actvivity back to its previous location in the Session.

If the baseline Activity is archived then there will no longer be a baseline for the Session. To set a new baseline select an Activity, right click, and select Set as baseline.


Feedback