Page History

...

Performance profiles can be used to achieve very specific control over the performance of virtual assets. The performance of each virtual asset can be set to reflect the dependent application’s actual performance or to simulate specific performance models that you want to test against. For example, you might want to simulate fixed response delays and response delay ranges—or ranges, or delays that are dependent on the hit-per-second rate that the application is under. For the load-dependent delays, you can utilize linear or exponential response template models; you can also create custom performance profile models using scripts. Additionally, when external applications are being monitored by an APM tool, you can import APM performance data into a profile.

...

Performance configurations (including performance profiles and performance groups) can be defined for each responder suite. Once a Virtual Asset is deployed on a Virtualize Server, you can map performance profiles to performance groups “on - the - fly” from either the Virtualize Server view or from CTP.

...

1. Open the responder suite’s configuration panel (i.e., by double-clicking the Virtual Asset Explorer node that is immediately below the .pva node).
   
2. Open the Performance> Performance > Profiles tab.
3. Click Add, then  and specify a profile name.
4. Configure the desired response delay. You can configure Fixed Response Delays, Range Delays, Load Dependent Response Delays, and Scripted Delays. See as described below for details.
   

When you’re done defining performance profiles, save the updated responder suite.

...

1. Set the delay type to Fixed.
2. Specify the desired delay value in milliseconds. Note that any think time or delay specified at the responder level will be added to the delay specified here.
3. Select the desired delay randomization: none, uniform, or Poisson.
   

Anchor
Range Delays Range Delays

Range Delays

...

1. Set the delay type to Load Dependent.
2. If you want to model performance using a graph other than the default one shown:
   1. Click the New Graph button below  below the graph.
   2. In the dialog that opens, specify the desired graph details (graph type, maximum hits per second, minimum delay [in milliseconds], maximum delay [in milliseconds], and number of points you can reposition). The Hit-per-Second rate is calculated as a number of requests per second to all responders of a Virtual Asset.
3. Modify the graph curve as needed by dragging the points.
   
4. From the Delay Randomization box below the graph, select the desired delay randomization: none, uniform, or Poisson.
   

Note that for all Hits Per Second (HPS) values that are greater than what is specified in the graph, the Response Delay value of the right-most graph point will be used. For instance, if the right-most key on the graph is 1500 milliseconds at 10 HPS (as in the graphic for step 3 above), all HPS rates greater than 10 HPS will use the 1500 millisecond response delay.

...

You can script the behavior of a performance profile. The scripting method should have the following characteristics:

• Return a number (i.e. int or long). This will be the delay time in milliseconds.
• Take 0, 1, or 2 arguments.
  • Argument 1 (if specified) will be the current hits per second on the responder. hps HPS is float type.
  • Argument 2 (if specified) will be the context object used by other scripting methods. The context argument is com.parasoft.api.ScriptingContext.
  

...

You can create any number of performance groups. Each responder can be included in no more than one performance group (i.e.that is, a single responder cannot be used across multiple performance groups).

...

1. Open the responder suite’s configuration panel.
2. Open the Performance> Performance > Groups tab.
3. Under Performance Groups, click Add, then enter a name for the new group/.
4. With the new group selected, click the Add under Responders.
   
5. In the dialog that opens, specify which responders belong to that performance group, then click OK.
   
   
   
   • Remember that a responder can belong to only one performance group. Enabling the Only show responders not associated with a performance group option will help you identify which responders are still available for assignment.

...

Once performance profiles and performance groups are set, you can apply them to virtual assets "on - the - fly" from either the Virtualize Server view or from CTP. This lets you quickly set and change the virtual asset’s performance conditions. 

...

1. Open the virtual asset’s configuration panel (i.e., by double-clicking its node).
2. Open the Performance tab.
3. Specify which of the available performance profiles you want to apply to each performance group.
   
4. Save the changes to the virtual asset.

...

• The responder level: Set in the Options tab under the Performance category. Note that the think time value can be parameterized against a data source column, if desired.
  
• The message level (only available in Multiple Responses mode): Configured for each message.
  

...

To query an APM system for available performance metrics and import selected metrics as performance profiles:

1. Click the Import button in the Performance tab of the .pva’s root Responder Suite. An Import Performance Profiles dialog will openopens.
   
   
   
2. From APM System, select the APM system from which you want to import data. Systems cur-rently currently supported "out - of - the box" are:
   • AppDynamics
   • dynaTrace
3. In the Query Properties table, set the appropriate query properties for your APM system. For details, see:
   • Importing Performance Profiles from AppDynamics
   • Importing Performance Profiles from dynaTrace
   
   The default property values are populated from the Performance Profile Importer deployment descriptors (described in Modifying Performance Profile Importer Deployment Descriptors). To modify the values in the Query Properties table, click the appropriate row in the Value column and edit the value. The values will be saved in the Responder Suite configuration after the Performance Profiles Importer dialog is closed with the OK button.
4. Click Reload (at the bottom of the dialog) to import performance data from the APM system. The available performance profiles will be displayed.
5. From the Create Profiles of Type combo box, select the profile types you would like to create.
   
   The following options are available:
   • Fixed: For each entry selected in the Import dialog, the importer will create a Fixed Response Delay performance profile. The profile’s delay value will be set to the Avg. Delay (ms) value as it appears in the Performance Profiles table of the importer dialog. The importer will append a _Fixed suffix to the names of the imported performance profiles.
   • Range: For each entry selected in the Import dialog, the importer will create a Range Response Delay performance profile with a delay range of Min. Delay (ms) and Max. Delay (ms) as they appear in the Performance Profiles table of the importer dialog. The importer will append a _Range suffix to the names of the imported performance profiles.
   • Fixed and Range: For each entry selected in the Import dialog, the importer will create a pair of Fixed and Range performance profiles as described above.
6. Select the profiles you want to import. You can use the Select All / Deselect All right-click commands in the Performance Profiles table to make multiple selections.
   If you selected performance profiles that do not have Max. or Min. delay values (because these values were not provided by the APM system), the Create Profiles of Type selection will be set to Fixed. Only profiles with Max. and Min. delay values can be used for a range delay type.
   
7. Click the OK button to import the selected profiles into the .pva’s Responder Suite performance configuration.
   If any profiles with the selected names and types already exist in the Responder Suite performance configuration, a warning and confirmation dialog will be displayed:
   
   If any profiles in the Responder Suite performance configuration have the same name as (but different type than) the profiles that are being imported, the import operation will be canceled, and the following dialog will be displayed. For example, if there is an existing Performance Pro-file Profile named “Calculator-Doc-Literal.subtract_Fixed” with a Response Delay of type Range, then importing “Calculator-Doc-Literal.subtract_Fixed” with Response Delay of type Fixed will not be allowed:
   

...

The AppDynamics Performance Profile Importer queries AppDynamics for performance data available in the Analyze> Analyze > Metric Browser node of application’s configuration and data tree. In the AppDynamics Metric Tree view, this data is displayed under the Business Transaction Performance> Performance > Business Transactions> Transactions > YourTier node and then under the Average Response Time metric node.

...

...

The default values which appear in the Query Properties table of the Import dialog can be customized by modifying the appropriate Performance Profile Importer deployment descriptor files. These files are located in the apm-integration/performance-profile-importers folder or the root directory directory (<INSTALL><INSTALL-DIR>/plugins/com.parasoft.ptest.libs.web_<VERSION>/root).

Modify the value attributes of the AppDynamics.xml and dynaTrace.xml Performance Profile Importer deployment descriptors as you see appropriate for your environment. 

...