| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Threads_servicing_jsp |
Current
number of active requests for the JSP
|
Number |
If a
majority of the threads/processes are in use simultaneously to serve
requests for a specific JSP, this may be indicative of a problem with
the design of this page. Further investigation is needed to determine
the cause of the bottleneck - whether it is the processing of the JSP,
whether it is a bottleneck in the database tier, whether the database
query (ies) are non-optimal etc. Alternatively, a slowdown of the application server may
also cause the requests that are simultaneously executing to increase. |
| Req_completed |
Rate
at which requests were processed by this JSP |
Reqs/sec
|
Comparing this metric across JSPs can indicate which pages are most
accessed. Optimizing the most heavily accessed pages can result in a
significant improvement in the user-perceived performance of that web
application.
|
| Avg_req_process_time
|
Average
time spent in servicing the JSP during the last measurement period |
Secs |
An
increase in this value may be indicative of a problem in the application
server/JSP logic. |
| Max_req_process_time
|
Maximum
time spent servicing a JSP since the server started |
Secs |
|