HTTP Listener map performance and throughput

You can analyze the HTTP Listener status information to tune the performance of Launcher systems. The status information includes response time details for URL watches that can indicate bottlenecks during peak load periods. It also displays details about connections, responses to the HTTP client, and logging.

The HTTP Listener status displays metrics that can be used to tune the Launcher performance.
Response time
The overall time to process an HTTP request for a particular URL.
Register time
The overall time to match an HTTP request with an available URL watch.
Map time
The average time to run the map and return a response to the HTTP Listener. Response time is approximately the sum of register time and map time.

The URL watch information displayed in the listener status is similar to the information in this table.:

Table 1. Example URL watch information provided as part of the HTTP Listener status
Watch # Busy Map Return HTTP Response Response Time Register Time Map Time URL
0 0 0 0 0.000 0.000 0.000 /admin
1 0 0 0 0.000 0.000 0.000 /admin/update
2 0 0 0 0.000 0.000 0.000 /admin/refresh
3 0 0 0 0.000 0.000 0.000 /admin/trace
4 0 0 0 0.000 0.000 0.000 /admin/trace/socket
5 0 0 0 0.000 0.000 0.000 /admin/audit
6 1 0 1 0.017 0.001 0.000 /admin/status
7 0 0 1 0.004 0.001 0.000 admin/reset
8 0 0 0 0.000 0.000 0.000 /admin/users
9 0 0 0 0.000 0.000 0.000 /admin/users
10 0 0 0 0.000 0.000 0.000 /admin/image*
12 0 1 1 0.531 0.001 0.528 /example

A significant increase in register time during peak load periods can indicate a backlog of HTTP requests. You can address a backlog by adding more copies of the map to the system (.msl) or by adding another Launcher to load-balance the HTTP requests.

The HTTP Listener status also includes the total number of success, failure, and unavailable responses that the HTTP Listener returned to the external HTTP client.

The Management Console displays this information in the Status page. You can also display it in a browser by entering the http://Launcher_host_address:http_port/admin/status URL. The dtx.ini configuration file controls the refresh interval of the information in the browser Status page. The Launcher refresh interval controls the refresh interval of the Management Console Status page.