Collecting Performance Data
Begin with creating a set of processes for testing purposes. These can be actual processes that will be used in production or more basic processes that represent the production scenarios. The granularity and scope of your performance requirements should determine how processes are used for performance testing.
Measure the memory, and CPU usage of the container during all tests. Identify the TIBCO ActiveMatrix BusinessWorks™ metrics that can measure conformance with requirements. A general strategy is to begin with summary metrics, and then progress to detailed metrics as areas for improvements are identified.
Configure the operating system tool to measure memory, disk, and CPU usage during all tests. Identify the Activematrix BusinessWorks metrics that can measure conformance with requirements. A general strategy is to begin with summary metrics, and then progress to detailed metrics as areas for improvement are identified.
However, if specific performance goals have been defined, you can tailor data collection to provide only required information. Understand where process instance lifetime is spent and collect detailed process instance metrics while processing a few representative process instances. Calculate total throughput, collect summary metrics while generating a typical number of incoming messages of typical size and frequency.
Conduct separate tests for minimum, desired, and peak target numbers. Wherever possible, restrict other local network, operating system, and engine activities during this time. If average metrics are used, restrict the test window to ensure that data collected is relevant.