eG Monitoring
 

Measures reported by BobiCRPSPerfTest

A healthy Crystal Reports Processing Server is one that processes all the page requests it receives without fail and in minimum time, so that EPF pages are quickly generated and returned to clients. If requests to a Crystal Reports, Processing Server fail often or take too long to be processed, EPF page generation will be considerably delayed. As a result, the server's promise of instant, page-on-demand access to users will stand broken, killing user confidence in its abilities. Moreover, any slowdown in request processing will also result in long pending request queues, which if allowed to grow may choke the server. In short, processing bottlenecks with the Crystal Reports Processing Server can prove to be detrimental to the health of the server and will also damage user experience with the server. This is why, it is imperative that administrators identify a probable slowdown or outage of the server at its nascent stages itself, so that they can avert such fatalities well before they occur. The BobiCRPSPerfTest test helps administrators with this.

This test closely tracks page requests to the server, continuously observes the rate at which the server processes page requests, rapidly isolates probable failures/slowdowns, and promptly alerts administrators to them. This way, the test provides administrators with a heads-up on potentially serious processing bottlenecks, so that administrators can work towards preventing them.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
requestServedRate Indicates the rate at which the server processes the page requests it receives. Requests/Sec A consistent drop in the value of this measure could indicate a probable processing slowdown.
openJobs Indicates the number of jobs that the server and its child processes are currently processing. Number This is a good indicator of the current workload of the server.
avgProcessingTime Indicates the average time taken by the server to process a request (taken over the last 500 requests). Millisecs Ideally, the value of this measure should be low. A high value or a consistent rise in this value is a cause for concern, as it indicates a slowdown in request processing.
queuedRequests Indicates the number of requests waiting to be processed or are being processed. Number A steady rise in the value of this measure is a sign of a request queue that is growing. This means that the server is unable to process page requests as quickly as it receives them. You may want to check the value of the busyServerThreads measure of the BobiCRPSStTest test to know if the lack of free threads in the thread pool is the reason for the slowness.
openConnections Indicates the number of connections open between the server and its clients. Number  
requestFailureRate Indicates what percentage of the last 500 requests have failed. Percent Ideally, the value of this measure should be 0. A non-zero value is a sign of trouble. A value close to 100 could hint at a critical problem condition that warrants an immediate and thorough investigation.
dataTransferRateKB Indicates the rate at which data is transferred from the server to its clients in the last measure period. KB/Sec