Share this page

# Performance Monitoring

You can monitor Service Virtualization performance and message processing using predefined performance metrics.

Once installed, you can monitor the performance using Windows performance counters or SiteScope monitors.

In this topic:

## Performance Categories

There are several Service Virtualization performance categories as follows:

Services | The Services performance counters provide measurement data per virtual service. Both the Designer and the Server write their data to these same counters. For details, see Services.
Operations | The Operations performance counters provide data per virtual service and service operation. Both the Designer and the Server write their data to these same counters. For details, see Operations.
Server Statistics | The Server Statistics performance counters provide data for a standalone Service Virtualization Server, and for the services deployed on the server. Only the Service Virtualization Server writes data to these counters. For details, see Server Statistics.
Server Thread Pools | The Server Thread Pools performance counters provide data about thread pools used by the Service Virtualization Server. For details, see Server Thread Pools.

The Services performance counters include the following:

Counter Name | Counter Description | Units
--- | --- | ---
Throughput | The data capacity of the virtual service. | MB/s
HitRate | The number of requests and responses processed by the virtual service. | hits/s
AverageResponseTime | The average time for the virtual service to process a request and return a relevant response. | ms
DataSimulationAccuracy | The accuracy of data model emulation of the real service by the virtual service. | %
PerformanceSimulationAccuracy | The accuracy of performance model emulation of the real service by the virtual service. | %

The Operations performance counters include the following:

Counter Name | Counter Description | Units
--- | --- | ---
Throughput | The data capacity of the virtual service operation. | MB/s
HitRate | The number of requests and responses processed by the virtual service operation. | hits/s
AverageResponseTime | The average time for the virtual service to process a request and return a relevant response for the operation. | ms

The Server Statistics performance counters include the following:

Counter Name | Counter Description
--- | ---
Connections | The number of connections from clients to Service Virtualization agents.
DbResponseTime | Communication latency between the Service Virtualization Server and the database.
HitRate | The number of requests and responses processed by all virtual services running on the Service Virtualization Server.
MessageSize | The average message size for all services deployed on the Service Virtualization Server.
Throughput | The average data capacity for all services deployed on the Service Virtualization Server.
TransactionsPerSecond | The average value for all services deployed on the Service Virtualization Server.

The Server Thread Pools performance counters include the following:

Counter Name | Counter Description
--- | ---
Threads | The number of threads in the thread pool.
ActiveThreads | The number of threads in the thread pool doing actual work.
WaitingJobs | The number of jobs waiting for the thread to be executed.

Back to top

## Performance Instances

Service Virtualization creates instances of all the performance counters for each virtual service that is deployed locally, either on the Service Virtualization Designer's embedded server, or on the Service Virtualization Server.

Instance names are created in the following format:

- For services: <service_name>
- For operations: <service_name>_<operation_name>
- For server statistics: server statistics. The instance is created during installation of the Service Virtualization Server. Data is updated on the Server machine only, when the Server is running.
- For server thread pools there are two instances—active thread pool and passive thread pool. Active thread pool is used for CPU intensive jobs, such as generating responses according to the simulation model. Passive thread pool is used mainly for waiting jobs such as receiving messages from the message bus.

For example, for a locally deployed virtual service called HelloWorld which has two operations named Hello and Bye, the performance counters in the local system have the following instances:

Counter Category | Counter Name | Counter Instance Name
--- | --- | ---
|  | Helloworld Service
Services | AverageResponseTime | helloworld
HitRate | helloworld
Throughput | helloworld
DataSimulationAccuracy | helloworld
PerformanceSimulationAccuracy | helloworld
|  | Hello Operation | Bye Operation
Operations | AverageResponseTime | helloworld_hello | helloworld_bye
HitRate | helloworld_hello | helloworld_bye
Throughput | helloworld_hello | helloworld_bye

Back to top

## Windows Performance Counters

Service Virtualization publishes performance related statistics to Windows performance counters. The performance counters are created during installation of either the Service Virtualization Designer or the Service Virtualization Server. Uninstalling the Designer or the Server deletes the counters.

Remote Monitoring

You can use the performance counters to monitor Service Virtualization that is running on a remote machine.

To remotely access the performance counters, you must use a Windows user account with appropriate privileges on the remote machine. You can create this account in the following ways:

Automatically | During installation of Service Virtualization, you have the option to create a user account that is automatically configured with the proper privileges. For details, see Installation.
Manually | If you create the Windows user account manually, you must add this user to the default Windows group Performance Monitor Users.

Troubleshoot Performance Counters

Some versions of LoadRunner Professional and LoadRunner Enterprise may not display the performance counters, due to an internal renaming issue.

If you experience this issue:

1. Open the Service Virtualization Server configuration file HP.SV.StandaloneServer.exe.config, located by default in C:\Program Files\Micro Focus\Service Virtualization Server\Server\bin\.

2. Make sure the following parameters are both set to "true":

   - <add key="SV.PerformanceCounters.UseHpPrefix" value="true" />
   - <add key="SV.PerformanceCounters.UseHpePrefix" value="true" />

Note: Performance counters can be read by domain users only.

Back to top

## SiteScope Monitors

You can view performance counters on Service Virtualization servers running on Linux in applications that support SiteScope integration, such as LoadRunner Professional and LoadRunner Enterprise. For details of these integrations, see the sections about SiteScope resource monitoring in the LoadRunner Professional and LoadRunner Enterprise Help Centers (select the relevant version).

The following configuration settings are used for the integration:

Setting | Description
--- | ---
Server | The machine on which the SV Server is running.
Port | The default SV installation uses port 6085 for a secured server and 6080 for an unsecured server.
Use HTTPS | Select this option for a secured server or leave unselected for an unsecured server.
Use Account | This setting is not used as SV does not required authentication.

When SV is integrated with LoadRunner Professional or LoadRunner Enterprise, performance counters are added automatically for SV services used in the integration scenario. This is not the case for an SV Server running on Linux for which you must add counters manually through the SiteScope integration described above.

Back to top

https://admhelp.microfocus.com Service Virtualization 8942
Tips to improve your search results... Service Virtualization Help Center SV Help 5.4-5.4.1 All View Local Help Center View Online Help Center back Go back in browser history forward Go forward in browser history Remove search highlights next topic Go to next topic previous topic Go to previous topic Print the current topic Version: