Overview of Creating Reports Using a Performance Task

Creating Reports Using a Performance Task

You define and execute a performance task for a SAS Model Manager project. The model that you monitor is always the champion model that is set in the default version folder for the project. The process of creating performance reports is a two-step process. First, you run the Define Performance Task wizard to generate the code that creates the reports. Then, you execute the generated code. SAS Model Manager stores the output data in the Resources folder of the default version. To view the resulting data, you select the Performance node in the default version.
To create performance reports in SAS Model Manager, follow this process:
  • Ensure that a performance data source is registered using SAS Management Console.
  • Ensure that all prerequisites have been completed.
  • Run the Define Performance Task wizard to generate the SAS code that creates the performance reports.
  • Execute the generated code.
  • To view the reports, select the Performance node in the default version.

Determine How to Use the Performance Data Sets

Before you run the Define Performance Task wizard, the performance data set must be registered in the SAS Metadata Repository by using SAS Management Console. For each SAS Model Manager project, you can set up your environment to use the performance data source that best suits your business process. Here are two methods of collecting performance data:
  • Method 1: You periodically take a snapshot of an operational data set to create a performance data set. Each time you take a snapshot, you give the performance data set a new name. Each performance data set must be registered in SAS Management Console. For each time interval, you name a new performance data source when you run the Define Performance Task wizard.
  • Method 2: You take a snapshot of the operational data set to create a performance data set over time, and you reuse the same name for each performance data set every time you take a snapshot. You register the performance data set with SAS Management Console only once. Each time you take a snapshot, you replace the performance data set at the location where the performance data set is registered in SAS Management Console.
    When you run the Define Performance Task wizard, the name of the performance data source does not change. Because you used the performance data source static name as the Default Performance Table in the project properties, the Performance data source box in the wizard is completed by SAS Model Manager.
The following table summarizes the tasks that are performed if performance reports are run after six months or for reports that are run every month. Use this task and example table to help you determine how you want to name your performance data sets and your SAS Model Manager performance data sources.
Task
Method 1: The Performance Data Set Name Changes
Method 2: The Performance Data Set Name Remains Static
Create a performance data set from model output data
Each month, take a snapshot of the operational data and create a performance data set with a different name:
  • Jul11
  • Aug11
  • Sep11
  • Oct11
  • Nov11
    Dec11
Every month, take a snapshot of the operational data and name the performance data set using the same name:
2011perf
Register the performance data set in SAS Management Console
Register the data sets monthly or register them all at once before you run the reports.
Register the data sets the first month only.
Modifications to make in the Define Performance Task wizard
In Step 3, select a performance data source, select a data collection date, and a date label.
In Step 3, select a data collection date and a date label.
The Performance data source field contains the static name of the performance data source name because it was specified for the previous execution of the task for this project.
Create the reports
For each performance data source, run the Define Performance Task wizard and execute the reports from the PerformanceMonitor project node.
Because each performance data source has a different name, you can run the performance task as desired; the task does not need to be run monthly.
Monthly, run the Define Performance Task wizard and execute the reports from the PerformanceMonitor project node.
To ensure that you do not write over important performance data, run the performance task before a new snapshot of the operational data is taken.